Omniscio

Sign back in to Claude when logged out

Sign back in to Claude from Settings → AI & Accounts → Accounts → Claude — the card for the sign-in method your sessions use leads you back in. New sessions start again once you are signed back in, and nothing else is affected. The automated re-login described below belongs to installs that balance work across several Claude accounts; a normal install signs in again by hand, exactly as above.

On this page

What it is

A Claude session cannot run without a working sign-in, and signing back in is one button on the right card. Open Settings → AI & Accounts → Accounts → Claude and use the card for the sign-in method your sessions run on:

  • Claude Code login (the default) — the card's button starts the sign-in, and it is the same button either way: it reads Sign in with your Claude account while no Claude Code login is on this computer, and Switch Claude account once one is. Clicking it signs you in again. The sign-in opens in its own window — finish it there and come back, then click Check again if the card has not caught up.
  • Sign in to Claude — click Sign in with your Claude account; the card then names the account your sessions run on. This method holds exactly one Claude account, so if the card still reads "Signed in to Claude" while your sessions will not start, click Sign out first and then sign in again; those same two steps are how you move to a different account.
  • Your API key — paste a new sk-ant-... key into the key field. A key Anthropic has turned down is replaced the same way.

Nothing but the sign-in is affected: your sessions, projects and settings are untouched.

Why it happens so often. Claude replaces an account's sign-in every time it is refreshed, so when two computers hold a copy of the SAME sign-in, whichever refreshes first leaves the other holding a dead one. That is the common cause for anyone with two machines, and it gets more common once cross-device sync or a backup restore copies sign-ins between them. Omniscio cannot tell which computer did it, so the warning on that row says "can happen", never "did". Signing the account in separately on each computer, instead of copying one sign-in across, is expected to give each computer a sign-in of its own; that has not been measured yet.

Everything below this point is the pooling pathway, and it is available only on the installs that already run one — those that were pooling several Claude accounts before this closed to new installs. Such an install gets a Sign them back in panel in that same Settings → AI & Accounts → Accounts → Claude tab, which drives the whole sign-in for every account the app has flagged as broken, and an optional setting that repairs a stale login on its own every few hours. A normal install — the Sign in to Claude method, your own Claude Code login, or your own API key — does not render that panel at all, so it has no Sign them back in button, no "N need re-login" badge and no automatic sweep: signing in again by hand, above, is the whole recovery. The command-line routes in For agents below are held to the same gate: they refuse the request and name the reason.

When a login in that pool goes stale, Omniscio flags it — that is the red row in Settings → AI & Accounts → Accounts and the "N need re-login" badge on the accounts popover. Repairing a few of them by hand is the genuinely tedious twenty minutes this automation exists to remove: open Chrome, start a sign-in, click "Continue with email", find the email, copy a six-digit code, paste it, and run Omniscio's own capture so the account is saved back into the pool — once per account.

What the badge counts. Every login the app itself has benched as unusable: a dead refresh token, an open auth breaker, a stale access token with nothing to renew it, or a persistent usage-fetch auth failure ("Auth token expired…", "OAuth organization blocked"). It is the same set GET /accounts/needs-relogin returns and the same set the automatic re-login targets, so the badge and the automation can never disagree about who is broken. The separate inbox card that tells you to sign in again is raised only when a login genuinely cannot authenticate — a bookkeeping escalation inside a running session no longer raises it.

Automated re-login does the whole thing for you. It drives your real Chrome for the page, clicks "Continue with email", reads Anthropic's sign-in email from the Google account you already connected, types the code, and clicks the final Authorize consent screen — then captures each account back into Omniscio. In the normal case you do nothing at all.

It used to ask you for two clicks per account, on the belief that Cloudflare rejects automated ones. That turned out to be false — measured 2026-09-07, every automated click across four accounts was accepted — so now it clicks first and only asks when its own click did not register. If that happens, the old behaviour is exactly what you get: it brings the page to you and waits.

Clicking Authorize for you needs "drive any tab" turned on (see below), because that consent window is one Omniscio opens through your operating system rather than a tab this tool made.

Where to find it

How to use it

  1. Open Settings → AI & Accounts → Accounts → Claude. Above the account rows there is a re-login panel. When any login needs re-login it says how many and offers a Sign them back in button; when they are all healthy it just says so, and that is where the automatic option below lives. If no Omniscio Chrome extension is connected, the panel says that instead and offers a Set up Chrome button, which opens the "My Real Chrome — Lite" switch in Settings → Features. A sign-in it cannot run is never offered.
  2. Click it. Omniscio works through the flagged accounts one at a time, in the background — its Chrome window stays behind whatever you are doing. It brings a Chrome page to the front only when Chrome is not running that page (Chrome pauses a window that other windows cover), and then only that one page. Before 2026-10-10 it brought the sign-in page forward on every account, and that is what stopped the emailed sign-in link from ever loading.
  3. Usually you do nothing. It is patient with a slow machine: it gives a page time to catch up after each click, waits out the Chrome connection dropping and coming back, and gives a sign-out a few minutes to land, rather than calling any of those a failure. If one of its own clicks genuinely does not register, it brings the Chrome page to the front and raises one inbox card ("Claude re-login — one click needed in Chrome") with a Show me the page button. Do that one click in Chrome.
  4. It carries on by itself the moment your click registers — no need to come back and tell it.
  5. At the end the card is replaced by the result: how many accounts are healthy again, and a plain-language line for any that are not.

Stop cancels a run mid-flight, and it genuinely stops: the email polling and page waits end immediately, the sign-in window it opened is abandoned, and every tab it opened is closed. Stopping also means it will not claim the account was fixed — a run that was cancelled before it could confirm anything says exactly that, rather than reading a badge that may have changed for reasons of its own.

Keeping them signed in without lifting a finger (optional, off by default)

The button above only helps if you notice a red row. If you would rather not have to, turn on "Sign them back in automatically" — the toggle at the bottom of that same panel.

With it on, Omniscio checks every three hours and runs the same sign-in for any account that has dropped out, so a stale login is normally repaired before you ever see the badge. A few things worth knowing:

  • It needs the Omniscio Chrome extension. The toggle alone signs nobody in: the sign-in is driven in your real Chrome, so "My Real Chrome — Lite" must be turned on in Settings → Features and its extension connected in Chrome. Lite is still marked in-development and is off by default. While no extension is connected, every check skips quietly — no window, no failed results, no alert — and the panel shows a Set up Chrome button. (Before 2026-10-16 each check ran anyway, failed every account within seconds and raised a failure alert; because the one-day wait was not remembered across a restart back then, every app restart produced another one. It is remembered now — see the fourth bullet below.)
  • Off means off. While the toggle is off there is no timer at all — nothing checks, and no browser window can open on its own. Turning it on takes effect straight away; turning it back off stops the next check immediately.
  • It only ever acts on an account that is actually broken. If every account is healthy it does nothing at all — no window, no card, no noise.
  • It will not hammer an account it cannot fix. If a whole run signs nobody back in — no sign-in mailbox, a Cloudflare click there was nobody to make — it waits a day before trying that again, instead of opening a browser every three hours. That day is remembered across restarts: closing and reopening Omniscio does not start the wait over.
  • You still do the one click Cloudflare insists on, exactly as with the button. If it needs you, you get the same single inbox card.
  • The first check happens a few minutes after Omniscio starts, not the moment it opens.

This is per-computer and per-person: nobody has it until they switch it on.

Omniscio opens the final Authorize screen through Windows, not through the browser connection — so as far as this feature is concerned it is a tab it did not create.

By default it is not allowed to see tabs it did not open. That is a deliberate privacy guardrail (it is the same rule that stops any agent looking at your banking or email tabs), and it has one consequence here: it cannot reach that Authorize window at all. Everything else still works — you just have to find the window in Chrome and click it yourself, and the run tells you so up front rather than leaving you watching a spinner.

If you would rather it handled that step too, turn on "drive any tab" for "My Real Chrome — Lite" in Settings. Lite is the one browser connection the re-login drives, and it reads that setting off Lite, so that is the only switch that matters here. Then it finds the Authorize window, brings it to the front, and clicks it for you, so the whole sign-in finishes without you. It waits a moment for that consent page to finish wiring itself up before clicking, because a click sent too early is ignored silently, and it re-checks afterwards — so if the click still does not land, the window is simply sitting there waiting for you, exactly as it would have been.

It will never turn this on for you. Widening what an agent can see in your browser is your decision, so the feature only ever reports which mode it is in.

How it behaves

Who can use it

Installs that balance work across a pool of Claude accounts — those that were already running a pool of several Claude accounts before this closed to new installs. A new install cannot turn it on: the panel is not rendered at all, no disabled button, no teaser, and nothing you can buy or switch on changes that. This is a compatibility gate on the pooled-accounts pathway, not a paid tier. Every surface on this page that belongs to the pool — the Sign them back in button, the "N need re-login" badge and the automatic sweep — is missing on an install without a pool, and the command-line routes refuse the request and name the reason. Signing in again by hand from the Claude tab in Settings is the whole recovery.

What it will never do

  • It never touches a tab it didn't open, with one deliberate exception. Your existing tabs — banking, email, anything — are untouched. The exception is Omniscio's own Authorize window, which it brings to the front and clicks so the sign-in can finish. That happens only if you have already turned on "drive any tab"; the tool never turns that on for you and never asks it to be. It matches only that one consent page, by exact address. With the setting off, nothing outside its own tabs is touched and it tells you so before it starts. See Letting it bring the Authorize window to you above.
  • It never logs, saves, or shows the sign-in link or the six-digit code. Not in a log file, not in the inbox card, not in an error message.
  • It never opens a link that isn't Anthropic's. The link's host must be exactly claude.ai, and the email must genuinely be from Anthropic — checked on the parsed sender address, so a lookalike or a spoofed display name can't redirect it.
  • It never opens a sign-in email meant for a different account. One inbox often receives the sign-in emails for many accounts. It only opens the one addressed to the account it is signing in, so it can't use up another sign-in's one-time link or sign Chrome in as someone else. An email whose recipient can't be read is still used, so a mailbox that hides it never stalls a run.
  • It never saves the wrong account and calls it a win. See below.
  • It never deletes an account.
  • It never throws away a sign-in it just earned. If Anthropic's profile endpoint is unreachable at the moment a sign-in completes, Omniscio cannot read which account it is, so it saves the credentials under a temporary unnamed row and settles the name later. When that happens while the account already exists, the sign-in's fresh credentials are folded onto the existing account before the temporary row goes — the account you just signed in keeps the only credential that works. And that unnamed row never takes over as the active account while another one is working, so live sessions are not pulled onto it.

The one thing to know about the Authorize window

Omniscio's account capture opens your default browser — which may not be the Chrome the tool is driving — and it saves whoever finishes that sign-in. If your default browser happens to be signed in as a different Claude account, a naive tool would save that account and report success.

This one doesn't. After every capture it checks the saved account's email against the one it was fixing. A mismatch is reported as a failure with both addresses named, and nothing is deleted — you sign out in that browser and run it again. The run also tells you up front, before you wonder, that the Authorize window opens in your default browser.

Adding an account you have not signed in before

Everything above is about REPAIRING an account Omniscio already has. The same machinery also adds one:

POST /accounts/relogin
{ "newAccountEmails": ["you@example.com"], "wait": true }

It signs that address in and saves it into your pool, using exactly the flow it uses for a repair — your real Chrome, the sign-in email read from your connected Google account, and the Authorize click. You can mix the two in one run: pass accountIds as well and it repairs those and adds these in the same pass.

Two things it will not do:

  • It will not add an address you already have. That is a repair, not an onboard, so it repairs that account instead of creating a second entry for it. An address you hold only as an API-key account has no sign-in to repair, so it is left alone.
  • It will not claim success it cannot prove. A repair can be proven by the red re-login badge clearing. A new account was never flagged, so no badge can clear — the only proof is a confirmed capture whose saved address matches the one you asked for. If it does not match, the run stops, tells you both addresses, and deletes nothing.

Before each account it checks who your browser is signed in as. If it is already the right account it leaves your session alone; if it is a different one it signs out first, because otherwise the sign-in it captures would be the previous account. The sign-out now clears the browser's claude.ai cookies directly, so it no longer depends on claude.ai's own logout page doing anything — that page stopped ending the session, which is what made every account after the browser's current one get skipped. Your Cloudflare clearance is left in place so the next sign-in is not challenged, and if the run is cancelled it clears nothing at all. It confirms the sign-out by asking claude.ai's session API, not by waiting for a page to render — on a busy machine a page can take minutes to paint while the API answers instantly. If it cannot tell who is signed in, it stops rather than guessing.

Why an account keeps getting signed out

When a pooled account's sign-in stops working for good, its row says so in plain words — in the toolbar account dropdown, on Settings → AI & Accounts → Accounts, and on the phone's account list: "This sign-in stopped working. That can happen when this account is also signed in on another computer. Log in again to use it here." The Log In button beside it is the one click. Both belong to the pool's account list, so an install that runs one Claude account sees neither of them — it signs in again from the Claude tab, and the "two computers" reason behind that sentence is the one given further up this page.

If something goes wrong

Read the account's own line — it names the step that failed. Every account in the results carries its own sentence, so you should not have to guess which part broke. Each message below is what you will actually see, followed by the fix.

  • "A re-login needs a connected Chrome bridge, and none is" — "My Real Chrome — Lite" is not connected, so there is no route to Chrome at all. Turn it on in Settings → Features (the panel's Set up Chrome button goes straight there), load and grant its extension, then try again. Lite is the only browser connection the re-login drives: the older "My Real Chrome" (Full) bridge is retired, and pairing it no longer helps. The run also says this in its notes BEFORE it starts, so you can stop it before it wastes any time. The panel does not list this line once per account any more: while no extension is connected it shows the one sentence and the button. (Until 2026-10-17 this message said "neither one is paired" and told you to pair either bridge.)
  • "no sign-in email for … arrived in … in time" — this one names two addresses on purpose: the account being signed in, and the mailbox that was watched. If mail for that account does not actually land in that mailbox, nothing will ever arrive — connect the Google account that does receive it (Settings → Connections → Google Workspace), or open the sign-in link yourself. This is the most common surprise on a machine other than the one this feature was built on.
  • "no Google account is connected" — it still works; it just cannot fetch the sign-in email for you, so it hands the code entry back to you.
  • "Chrome is not drawing the sign-in page … bring the Chrome window to the front" — Chrome would not run one of the pages even after Omniscio brought it forward, usually because the window is minimised or Windows refused to bring it up. Click the Chrome window once and re-run. (Until 2026-10-10 this case was reported as "the page never finished loading", "never showed a login code" or "never signed in", which sent you looking at the wrong thing.) Tip for a fully hands-off run: Chrome's own "Enable Window Occlusion" policy, switched off, keeps covered windows running so nothing ever needs to come forward — measured with the policy off, a covered sign-in page then loaded in 5 seconds instead of not at all.
  • "the sign-in page never finished loading" — the page answered but never became the sign-in form in time. Check the browser is alive and re-run that account.
  • "the sign-in page never moved past the Continue with email step" — nobody clicked it inside the five-minute window. Re-run and watch for the page it brings to the front.
  • "the sign-in link had already expired" — Anthropic's links last about ten minutes. Just run it again to get a fresh one.
  • "the page behind the sign-in link never showed a login code" — the link opened something unexpected. Re-run that account.
  • "the login code could not be typed" — the code box was not on the page. Re-run; if it keeps happening, the sign-in page has changed shape and the tool needs updating.
  • "the sign-in box never took the login code" — the code was typed but the page did not register it, so nothing was submitted. Re-run; if it keeps happening, paste the code into the box yourself. (Until 2026-11-11 this read as "the browser never signed in", which sent you looking at the browser instead of the box.)
  • "the code was in the box but the Verify click did nothing" — the click was sent and the page ignored it. Bring the Chrome window to the front and click Verify yourself.
  • "the login code went in but the browser never signed in" — the code was rejected or the page never moved on. Re-run that account.
  • "signed in, but the Authorize step was never confirmed" — the sign-in worked; the consent window is the part that did not finish. Switch to Chrome and look for the Claude consent tab, or turn on "drive any tab" (above) so it can bring that window to you next time.

See also

Last verified 2026-11-08