Skip to content

fix(pairing): add auth token input for non-loopback websocket#5

Merged
DonPrus merged 2 commits intomainfrom
codex/issue-2-ws-auth-token
Mar 3, 2026
Merged

fix(pairing): add auth token input for non-loopback websocket#5
DonPrus merged 2 commits intomainfrom
codex/issue-2-ws-auth-token

Conversation

@DonPrus
Copy link
Contributor

@DonPrus DonPrus commented Mar 2, 2026

Summary

  • add an optional auth_token input on the pairing screen
  • append token query param to WebSocket URLs when the token field is provided
  • redact token in diagnostics modal output to avoid leaking secrets in UI
  • document the non-loopback token flow in README and operations docs

Why this is the right fix for #2

  • keeps the endpoint field simple (ws://host:port/ws) and removes the need for users to manually craft query params
  • still supports existing URLs that already include ?token=... (does not overwrite them)
  • works for local pairing, reconnects, and session restore flows

Testing

  • npm run test
  • npm run check
  • npm run build

Closes #2

@DonPrus DonPrus merged commit 709a4b9 into main Mar 3, 2026
1 check passed
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.

Can't connect: WS connection rejected: token required for non-loopback bind

1 participant