Show what autoconnect will reconnect to, under the option #124

New issue

Open

opened 2026-08-22 23:57:02 -04:00 by mysticalsoap · 0 comments

mysticalsoap commented

2026-08-22 23:57:02 -04:00

Owner

Enabling autoconnect resurrects every role recorded in last_server.json -- main, hop, and bypass -- and nothing in the ui shows that standing intent until it fires. First real use surprised: a bypass entry declared during the #75/#76 testing wave (only kill_bypass clears it; restarts and network changes deliberately don't) auto-connected a bypass tunnel to us-va-162 that nobody remembered asking for.

Smallest fix: under the autoconnect option, list the current reconnect targets per role ("main: us-nj-130 · bypass: us-va-162"), so the declared state is visible where it's armed. Fits the preferences-vs-commands framing from #67 -- a preference the ui never shows is a hidden mode; this is the residue case (declared intent outliving the memory of declaring it).

Candidate for the wider ux overhaul rather than a one-off, but cheap enough to do standalone.

Enabling autoconnect resurrects every role recorded in `last_server.json` -- main, hop, *and* bypass -- and nothing in the ui shows that standing intent until it fires. First real use surprised: a bypass entry declared during the #75/#76 testing wave (only `kill_bypass` clears it; restarts and network changes deliberately don't) auto-connected a bypass tunnel to us-va-162 that nobody remembered asking for. Smallest fix: under the autoconnect option, list the current reconnect targets per role ("main: us-nj-130 · bypass: us-va-162"), so the declared state is visible where it's armed. Fits the preferences-vs-commands framing from #67 -- a preference the ui never shows is a hidden mode; this is the residue case (declared intent outliving the memory of declaring it). Candidate for the wider ux overhaul rather than a one-off, but cheap enough to do standalone.

mysticalsoap added the

label

2026-08-22 23:57:02 -04:00