Repository navigation
Pair this computer: hand the CLI the app's own LAN connection - #39
Merged
Merged
Conversation
With two pods on USB and the app on the LAN (192.168.1.164 or benchpod-c2f662.local), Pair ran `--connection usb lan-clients add`, which asked which pod. A LAN address or name now goes to the CLI as it is: the CLI (benchpod-cli#84) pairs over that pod's own USB link. usb:<name> and embeddedci:<name> stay. The panel shows the CLI's error without the "[benchpod]" prefix. benchpod-xxxxxx.local gives the pod's name, and a bare benchpod-xxxxxx goes to the MCP server as benchpod-xxxxxx.local, so it connects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found testing 0.2.2 with two pods on USB: the app was on the LAN (192.168.1.164, or benchpod-c2f662.local) and "Pair this computer" ran
benchpod --connection usb lan-clients add, which refused with "2 pods on USB ... pick one", shown raw.--connection 192.168.1.164 lan-clients add. The CLI (lan-clients add over a LAN address pairs through the pod's USB link benchpod-cli#84) reads the pod's status and pairs over that pod's USB link. The server takes a LAN connection only when it is the app's own.usb:<name>andembeddedci:<name>unchanged.[benchpod]and the command's name.benchpod-xxxxxx.local(andusb:benchpod-xxxxxx.local) give the pod's name. A barebenchpod-xxxxxxgoes to the MCP server asbenchpod-xxxxxx.local(the SDK otherwise asks the OS resolver and fails with "nodename nor servname provided").Tests: Go (argv per connection, LAN only for the app's own, error text, mcpConnection) and vitest (LAN pairing posts the app's connection and shows the message).
🤖 Generated with Claude Code