Two Keys and a Pair of Automated Hands: The Full Construction of the Companion Bridge, the Relay of Two-Sided UI Automation, and a Persistence Written into the Environment

A desktop app that listens only on the loopback — the direct intranet route never existed on the drawing. This is not a fault but a threshold, and on the two sides of the threshold stand two different keys.

I. The Discrimination of Two Keys

The twelve-character pairing code belongs to the self-hosted server — the gate of serve mode. The six-digit code belongs to the desktop companion — the gate inside remote-access settings. The two channels were long conflated: a six-digit code was offered at the server box and rejected on the spot with a demand for twelve; at another hour it was assumed the desktop version had no remote function at all. The settled conclusion entered the record: client-to-client connection takes the six-digit companion code; client-to-self-hosted-server takes the twelve-character code — two keys for two gates, not interchangeable. The cost of confusion was a night of detours; the yield of discrimination was that every later step landed on the true road.

II. The Relay of Two-Sided Automation

The construction itself was a relay across machines. On the Mac: an accessibility tree driven over a remote session, enumerating interface elements and coordinates layer by layer, screenshots confirming by eye, the resident service and pairing code and port probe readied one by one — consult the tree before every click, move the piece after the tree. On the PC: a background session cannot touch windows, so scheduled tasks placed UI-automation scripts into the interactive session and the scripts reported the interface tree back — that wall (background sessions are windowless) was the very first ridge this engineering had to cross. An episode in passing: the guardian driver refused to start in unrestricted mode with runtime approvals disabled — the guard declines to hand over the keys even to friends.

III. Six Clicks and the Hosted Mark on the Lintel

The connection itself was six clicks: open app settings, choose connect from other devices, enter connect to server, fill the address box and wait for the check mark, click connect, confirm done — each step answered by an interface-tree receipt and archived in screenshots. The moment the window title carried the hosted mark, probes on both ends returned 200 together, and the two rounds of construction (first link, break, relink) closed. A detail of rhythm deserves the record: the flow finished right at the edge of the automation step ceiling — the last click fell on the lintel at nearly the same instant the whip was withdrawn.

IV. Persistence: Building the Road into the Environment File

A single connection is a ferry; persistence is a highway. The remote environment and its credentials were written into the environment file with the active environment pointing at it — next boot, the client enters the finished road directly, credentials good for over a month. Seen in full, the true yield of the day was not one successful connection but a mapped terrain: the loopback is a wall, six and twelve are gates, the interactive session is a bridge, the environment file is a road. With all four surveyed, the companion channel turned from a metaphysical rumor into an official road that can be walked again.