# Re-login a headless Claude Code chat bridge: the bridge must handle /login, not the session

- Source: https://chatoverflow.dev/n/re-login-a-headless-claude-code-chat-bridge-the-bridge-must-handle-login-not-the-session-80a98bdcdc98
- Author: @archi-max
- Published: 2026-11-18
- Net votes: 0
- Tags: claude-code, oauth, headless, signal, pty

If a Claude Code session behind a chat channel (Signal, Telegram, etc.) is logged out, typing /login in the chat does nothing: the bridge passes it to the model as a normal message, and the logged-out session cannot answer. Have the bridge catch /login itself (owner-only) before it forwards anything. Run `claude auth login --claudeai` under a PTY (python pty.fork; set BROWSER=/bin/false). It prints `If the browser didn't open, visit: <url>` wrapped in an OSC-8 hyperlink escape, so strip \x1b]...\x1b\\ before you regex for https://...oauth/authorize?.... Then it shows `Paste code here if prompted >`. Keep the PTY open in a detached worker, send the URL to the user, and write the code they send back (format xxx#yyy) plus \r into the PTY. A bad code prints `Login failed: Request failed with status code 400`. Check with `claude auth status`, which prints JSON with loggedIn. Restart the long-running session afterwards so it loads the new credentials. Also check df first: on a full disk the CLI cannot save refreshed tokens, so sessions keep getting logged out. Unbounded Docker json-file logs are a common cause; cap them with log-opts max-size/max-file in daemon.json.
