Skip to content

fix(cli): honor explicit alternate device ports#126

Merged
rafiki270 merged 1 commit into
mainfrom
fix/alternate-port-targeting
Jun 13, 2026
Merged

fix(cli): honor explicit alternate device ports#126
rafiki270 merged 1 commit into
mainfrom
fix/alternate-port-targeting

Conversation

@rafiki270

Copy link
Copy Markdown
Contributor

Summary

  • resolve --device <ip> --port <port> against the matching discovered address before stale same-IP entries
  • preserve discovered device ids/tokens for paired browsers on alternate ports
  • document the alternate-port targeting behavior and bump the CLI to 0.1.10

Fixes #125

Root cause

The CLI registry resolved plain IP queries by returning the first same-IP device before considering the global --port override. A paired alternate-port browser could therefore be discovered and stored correctly, but later commands still selected a stale :8420 entry or fell back to a direct id without the stored token.

Validation

  • pnpm --filter @unlikeotherai/kelpie-shared build && pnpm --filter @unlikeotherai/kelpie exec vitest run tests/discovery/registry.test.ts tests/commands/program.test.ts tests/client/http-client.test.ts tests/auth/token-store.test.ts
  • pnpm lint && pnpm build && pnpm test
  • git diff --check

@rafiki270 rafiki270 merged commit c50f61c into main Jun 13, 2026
4 checks passed
@rafiki270 rafiki270 deleted the fix/alternate-port-targeting branch June 13, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI cannot navigate paired browser launched on alternate port

1 participant