Account re-login over HTTP — `POST /accounts/login-capture`
The HTTP twin of the account panel's general Log In button: how an agent starts an Anthropic account re-login through Omniscio's local control server, polls until the flow finishes, and confirms which account was captured. Covers the two routes, the full headless sequence, every error status, and the credential-safety gates wrapped around it.
On this page
What it is
How an agent completes an Anthropic account re-login end to end over the CLI control server, without a human driving the desktop UI. This is the HTTP twin of the account panel's general "Log In" button.
Where to find it
The thing being driven here is the account panel's general "Log In" action, which sits in the footer of the account indicator — the small account strip in the app's chrome — and not the per-account orange re-auth buttons beside it. Everything else on this page is addressed to an agent working over HTTP rather than to someone clicking in the desktop UI.
How it behaves
What the "Log In" button actually does (and which browser it signs into)
The account panel's general "Log In" action — the account-agnostic one in the AccountIndicator footer, NOT the per-account orange re-auth buttons — starts a PKCE OAuth flow via authService.login():
- It opens the system default browser (through
shell.openExternal) to Anthropic's authorize URL, and starts a loopback HTTP server to catch the OAuth redirect. - It is account-agnostic: whichever Anthropic account finishes the sign-in is the one captured — Omniscio identifies the account from the tokens the callback returns.
- It signs into the system default browser — not a managed login window, and not the Real Chrome bridge / the user's real Chrome over CDP. So step 2's magic link must be opened in that same system-default-browser OAuth flow.
- It imports a completed OAuth callback, never browser cookies. There is no "paste cookies to sign in" path.
That last point is why the endpoint below must be started before the magic link is opened — the OAuth callback can only complete a flow that is already running.
Related
The wider account and sign-in picture — the account indicator, switching accounts, and what the orange per-account re-auth buttons do — is on the account indicator and account re-login pages. How a session's credential actually gets chosen, and what the managed-versus-own-key gate means, is on the auth pathways page. For driving Omniscio over HTTP in general, rather than this one route, start from CLI control.
Last verified 2026-09-23