Browser Logins (log in once, keep the signed-in browser)
Log into a site once by hand and Omniscio keeps that signed-in browser profile: open it signed in inside Omniscio's own browser pane, or import it into Agent Web's saved logins so every agent can use it. Covers the panel and how to capture a login, why passkeys cannot be used in the capture window, how agents get a saved login now, the three freshness checks, and what is stored where.
On this page
What it is
Browser Logins lets you open a browser, log into any site(s) you want, and close it — Omniscio captures that login automatically (naming it after the site) and keeps it until the site signs you out. You can open it signed in inside Omniscio's own browser pane, or import it into Agent Web's saved logins (Settings → Agent Web → Saved logins), which is how agents use a site you are signed into — many at the same time, each in its own copy. It's local-only: no passwords are stored, and nothing leaves your computer.
It's available to everyone — there's nothing to turn on. Reach it two ways (same panel either
way): Settings → Browser Logins, or the Agent Tools → Browser Logins row in the sidebar
(nested alongside API Keys — both are credential surfaces). The browser-automation
tool it uses (agent-browser) is installed for you automatically during first-run setup.
This is a separate surface — it does NOT change how Claude Code sessions, the active account, or any provider you've connected behave. It's a saved browser session; agents reach it only once you import it into Agent Web.
Key facts
- No passwords stored. Omniscio saves the browser session (cookies/profile) you create by logging in by hand — never your password. Everything stays on your computer.
- Local-only + revocable. Remove a login and its master profile + every clone are deleted from disk. (Removal is permanent — there's no undo.) A copy you imported into Agent Web's saved logins is separate and stays until you remove it there.
- On by default, and switchable off. Nothing has to be revealed — the feature is available to
all users out of the box, and nothing is shared or happens until you deliberately add a login.
To turn the whole surface off, flip its Settings → Lab toggle (
browserLoginsEnabled); that setting is live, so the sidebar row and the CLI routes go away with it. The browser-automation tool it needs is installed automatically during first-run setup (best-effort; add it later from Settings → Connected Tools if that ever fails). - Desktop-only capture. Adding a login needs a desktop Chrome window; the list, the usage log and removal also work from a phone.
- Imports your old logins (copy, never move). If you set logins up in Omniscio's earlier agent-browser tool, one Import click adopts them into Browser Logins; the original store is never written, moved, or deleted, so the old tool keeps working too.
- Not the same as the AI Browser's autofill vault. That's a separate, unrelated feature — an encrypted password manager for your own tabs inside the (also in-development) AI Browser panel, with zero agent or CLI access. This page's Browser Logins keeps whole signed-in browser profiles, which agents use only after you import them into Agent Web. See ai-browser.md for the comparison table.
Where to find it
There are two doors to the same panel: the Browser Logins section inside Settings, and the Browser Logins row in the sidebar under Agent Tools, where it sits next to the key vault because both are credentials your agents reuse. Browser Logins is desktop-only: capturing a login needs a desktop browser window and every Browser Logins call is refused on the phone link, so the sidebar row does not show on a phone.
What you see on the screen
Open it from Settings → Browser Logins or the Agent Tools → Browser Logins sidebar row. The panel (identical on both) has:
- No setup toggle — Browser Logins is on for everyone, so there's no "enable" switch; the panel below is the feature (nothing is shared until you add a login).
- Saved logins — each saved login shows its name, an Enabled/Disabled pill, the site, and when it was added / last used, with a per-row rename (the pencil), an enable/disable toggle, and a Remove button. Empty until you add one.
- Add a login — one click opens a real Chrome window at a blank page; you go to any
site(s) you want, log in by hand, then close the window and Omniscio saves the session, naming it
automatically after the site you logged into (rename it later from the list if you like).
There's no form to fill in. The dialog streams live status
("Opening browser… → Waiting for you to log in… → Saved!") plus a Cancel that also closes the
window. Desktop-only — capture needs a real browser window, so on a phone the section is
read-only (list / usage / remove stay usable; Add is disabled).
- Passkeys do not work in that window — use a password. Chrome switches WebAuthn off whenever a browser is being driven by an automation/debugger connection, which is exactly how this capture works; a passkey attempt is refused instantly and no Windows Hello / Touch ID prompt appears. The dialog says so, because the browser still advertises passkey support and sites will happily offer an option that can never complete. This is a deliberate Chrome protection against credential theft and is not something to work around. Passwords, 2FA codes, and email magic links all work normally.
- A login you finished is never thrown away. Closing the window is detected within a few seconds and saves immediately; and if a capture runs past its ten-minute ceiling (a slow 2FA, a password reset), the finished login is still kept rather than discarded. Nothing is saved if you press Cancel, if no session cookies were created, or if the window only ever showed a sign-in screen.
- Import existing logins — if you already set up logins with Omniscio's older agent-browser tool, a card appears naming them (e.g. "google, porkbun") with an Import button. One click copies them into Browser Logins, where they work like a captured login. Your originals stay exactly where they are (untouched), importing twice does nothing, and it works on a phone too — it's just a file copy, so it needs no browser window and shows even if the capture tool isn't installed. The card only appears when there's something to import.
- Usage log — a read-only record of which agent (or the CLI) used which login, and when.
If the underlying tooling isn't ready (Omniscio's agent-browser helper or a real Google Chrome is missing) a panel explains what to install and disables Add.
How it behaves
How agents get a saved login
Agents no longer open Browser Logins themselves. An agent reaches the web only through
Agent Web (amc-web), which keeps its own saved logins: each agent's browser starts
signed in to every site saved there, many agents at once, each in its own copy. To hand agents a
login you captured here, open Settings → Agent Web → Saved logins and click Import on the line
"You have N Browser Logins that agents can use here" — it copies them in and leaves Browser Logins
exactly as it is.
The old agent road is retired: the bundled amc-browser use <name> command, the saved-login names
Omniscio used to inject into every agent's instructions, and the two agent routes behind them. A
session started by an older build that still has those variables simply finds them stripped.
Omniscio still opens a login's clone when you use it in the in-app browser and when it checks that a login still works. Each clone runs headless — no window opens, on your screen or off it. That is the default and there is no in-app control to reveal one. The trade-off is real and worth knowing: a headless clone can get stuck on "prove you're not a robot" gates like Cloudflare, so if opening a login stalls on a site that challenges it, that is the likely cause rather than a bug.
A developer who needs to watch a clone work (or to clear a challenge that genuinely needs a real
window) opts in per-run with the environment variable AMC_BROWSER_LOGINS_HEADED=1. Two things
stay headless regardless: an e2e/sandbox instance (AMC_INSTANCE_ID), and any run with the
AMC_BROWSER_LOGINS_FORCE_HEADLESS kill switch set. Be aware that the headed window is a real
window on your screen, sitting over whatever you were doing. It cannot be hidden or parked
off-screen: the underlying agent-browser CLI treats a comma as an argument separator, so Chrome's
--window-position=x,y arrives mangled and is ignored — headed and invisible are mutually
exclusive, which is exactly why headless is the default. Only turn it on for the run that needs it.
Using a saved login in the in-app browser
Note: the in-app AI Browser referenced below is live again — retired on 2026-08-02 and un-retired on 2026-08-31, it sits behind its own
ai-browserLab toggle (Settings → Lab, off by default) and works once you turn it on. If you would rather drive a browser you are already signed into yourself, the road for that is My Real Chrome (a companion extension drives your own signed-in Chrome, tabs it opens itself). Saved Browser Logins themselves (above) are unaffected either way.
A saved login can be used in Omniscio's in-app AI Browser (itself in-development, behind the same kind of Lab flag) by opening it in one of your own tabs:
- From Settings → Browser Logins. Each login's Use in app button opens a Browser tab already signed in with it. The tab gets its own private space (a per-login partition) so it never mixes with your normal in-app browsing, and it is only ever filled from a login you captured, never from your own everyday browsing. (The button used to open a menu whose other item signed the pane's agent tab in with the login. No agent drove that tab after agents moved to Agent Web, so the agent tab and that item are retired, and the button does the one thing left.)
- From the Browser pane (no Settings trip): with Browser Logins on, its toolbar shows an "Open signed in"
control (key icon) that opens the pane already signed in on the login's partition — one login
opens on click, multiple show a picker, and a "Signed in as <name> · Exit" indicator returns you to
normal browsing. It needs only the
browser-loginsflag, so it works in the plain single-page pane too (see Embedded Browser → Google sign-in caveat).
Honest caveat — this is best-effort and cookies-only. The in-app browser is a different engine
than the real-Chrome profile the login lives in, so a saved login is applied there by copying its
cookies (the full session, http-only auth cookies included) into the in-app browser — it does
not carry localStorage/IndexedDB, and it can't refresh a token that rotates. So:
- Ordinary cookie-session sites work in-app.
- Some single-page apps and certain Google surfaces keep their sign-in in
localStoragerather than cookies, so they may still show logged-out in-app, and a rotating token can go stale — for those you may need to re-log-in by hand in the in-app browser. - If nothing could be copied, the tab just opens logged-out — it never errors.
- Agents are unaffected — a login you imported into Agent Web lives there as a full browser profile (the complete, most-reliable path), which carries everything cookies alone can't.
Login freshness (does the saved login still work?)
A saved login lasts until the site signs you out. Three signals keep a stale one from silently failing you:
- Verify on save — capture won't save a login that never got past a sign-in screen (you closed the window without finishing). Conservative: it never discards a login you actually completed — any doubt, it saves. So a bare sign-in page can't be frozen and handed on.
- Expiry check on use — opening a login in the in-app browser reports a
loginState(ok|expired|unknown).expired= the saved cookies no longer authenticate (the clone opened on a sign-in page); the browser still opens, but you know it's logged out instead of finding out later. Best-effort; never blocks the use. - Keep-warm (proactive) — a background job (~6-hourly) probes each stale login and, when one is signed out, raises a single inbox alert ("re-capture X" → Settings → Browser Logins) so you fix it before you need it. It probes via a throwaway clone — the saved master profile is never opened or modified.
Invariants for all three: browser-logins-reliability-contract.md.
Related
How agents browse, including the saved logins they use and the Import from here, is on the Agent Web page. Driving a browser you are already signed into yourself, through your own Chrome rather than a clone, is a different mechanism described on the My Real Chrome page. The in-app browser these logins can also be pointed at, including its own separate autofill vault for your own tabs, is on the AI Browser page.
Last verified 2026-10-17