tui: /pair QR code encodes the loopback 127.0.0.1 link, so other devices cannot connect #58810

Activity

1. opencode-agent commented on Oct 24, 2026

   

   opencode-agentBot

   on Oct 24, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report. I reproduced this on v2.1.4, and it still happens on the latest dev (13a615b).

   Steps:

   1. Bind the service to 0.0.0.0. server.info().urls then lists http://127.0.0.1:<port> first, followed by the LAN address.
   2. Open /pair in the TUI.
   3. Decode the QR code. It decodes to http://127.0.0.1:<port>/auth/connect/<code>, even though the LAN link is listed right next to it.

   The dialog also still shows the "Run opencode service set hostname 0.0.0.0" hint when the service is already bound to 0.0.0.0.

   The cause is that dialog-pair.tsx builds the QR from the first link, while opencode pair filters out loopback addresses first. Open PR #54051 addresses this. #54871 is the separate issue about the CLI QR containing JSON instead of a plain URL.

   The recording and screenshots below show the dialog, and the script below reproduces it. Until this is fixed, opening the LAN link from opencode pair (or from the dialog's link list) works.

   recording.mp4

   

   

   Reproduction script (drive.ts)

   // Reproduces #58810: the TUI /pair QR code encodes the loopback link.
   // The service is bound to 0.0.0.0 (via a wrapper), so server.info() lists
   // 127.0.0.1 first, then the LAN address(es).
   import { Effect } from "effect"
   import { OpenCodeDriver } from "opencode-drive"
   import { chmodSync, writeFileSync } from "node:fs"
   
   // Wrapper that runs opencode (release from PATH, or the checkout in $OC_DEV) and
   // binds the service to 0.0.0.0, as `opencode service set hostname 0.0.0.0` would.
   const wrapper = "/tmp/opencode-58810-wrap.sh"
   writeFileSync(wrapper, "#!/usr/bin/env bash\nif [ -n \"$OC_DEV\" ]; then\n  run=(bun --conditions=browser --preload=\"$OC_DEV/packages/tui/node_modules/@opentui/solid/scripts/preload.js\" \"$OC_DEV/packages/cli/src/index.ts\")\nelse\n  run=(opencode)\nfi\nif [ \"$1\" = \"serve\" ]; then shift; exec \"${run[@]}\" serve --hostname 0.0.0.0 \"$@\"; fi\nexec \"${run[@]}\" \"$@\"\n")
   chmodSync(wrapper, 0o755)
   
   export default OpenCodeDriver.use(
     {
       opencode: { command: [wrapper] },
       tui: { recording: true, keypressOverlay: true, viewport: { cols: 140, rows: 50 } },
     },
     ({ ui, opencode }) =>
       Effect.gen(function* () {
         const info: any = yield* opencode.server.info()
         yield* Effect.log(`server.info().urls = ${JSON.stringify(info.urls)}`)
         yield* ui.screenshot("home")
         yield* ui.type("/pair")
         yield* Effect.sleep(500)
         yield* ui.enter()
         yield* Effect.sleep(1500)
         yield* ui.screenshot("after-enter")
         yield* ui.waitFor("Links", { timeout: 15000 } as any)
         yield* Effect.sleep(1500)
         const frame: any = yield* ui.capture()
         yield* Effect.log(`screen:\n${frame.lines.map((l: any) => typeof l === "string" ? l : (l.text ?? JSON.stringify(l))).join("\n")}`)
         yield* ui.screenshot("pair-dialog")
       }),
   )

   Run it with opencode-drive: opencode-drive run ./drive.ts. It drives opencode from your PATH; set OC_DEV to the path of an OpenCode checkout to run that from source instead.
2. opencode-agent

   added

   reproduced

   on Oct 24, 2026