Does Solari Work With 1Password for Agent Logins?
Does Solari work with 1Password for agent logins?
Solari signs browser agents in with a read-only 1Password service account, filling username, password and TOTP codes without exposing the credential.
Yes: Solari works with 1Password, signing a browser agent in to your sites by reading a read-only 1Password service account and filling the username, password and one-time code at the login page.
What Is Solari Auto-Login With 1Password?
Auto-login is a Solari Cloud Browsers feature that signs an agent in to sites you own without anyone handing the agent a password, as the Sign in with 1Password guide describes.
Solari connects to 1Password through a read-only service account that you create once.
When a session reaches a login page for a site you set up, Solari fills in the username and password, then submits the form.
If the site then asks for a one-time code, Solari types that code too.
How Does Solari Decide How to Sign In?
Solari tries three methods in order at a login page and stops at the first one that works.
First comes a saved session: a browser that is already signed in, for example through a profile, needs no credential at all.
Second comes 1Password: Solari reads that one login from the vault and types it into the form.
Third comes a person: Solari hands the session to a human through a link with a plain reason, the person finishes in the live browser, and the agent carries on.
Does the Agent Ever See the Password?
The agent gets back the outcome of the sign-in, never the credential.
Solari reads the password at the moment it types it, holding it in memory for that one fill.
The password is not stored, logged or returned by any API, according to the auto-login security notes.
While Solari signs in, recording of the page pauses, so a session replay never captures what was typed.
How Do You Connect 1Password to Solari?
Create a read-only service account in 1Password under Developer, Infrastructure Secrets Management, Create a Service Account, with access to only the vaults your agents should use.
Store each login as a 1Password Login item whose Website field holds the login page address, which is how Solari finds the item.
Paste the service account token, which starts with ops_, into the Solari console under Settings, Connections, Password Manager, Connect 1Password.
Solari checks the token against 1Password before saving it and shows exactly which vaults it can read.
How Do You Add a Site for Auto-Login?
Each site points at a password manager connection before Solari signs in to it.
Under Sites, choose Add a site, enter the host such as github.com, and set Sign in using to your 1Password connection.
Leave the Vault/Item field blank to let Solari find the login by site, or set it when one site has several logins.
Each site shows its state in the console: Not signed in yet, Signed in or Session expired.
Does Solari Fill One-Time Codes From 1Password?
Add a one-time password field to the 1Password Login item and Solari computes the current TOTP code, then types it at the prompt.
Solari matches items on the site's host, so an item saved for example.com also serves login.example.com.
SMS codes, email codes, passkeys and hardware keys go to a person through the hand-off link, as the one-time code section explains.
How Do You Turn On Auto-Login in a Session?
Create the session over the Solari API with autoLogin: true, then connect your usual client to the returned wsEndpoint or cdpEndpoint.
Solari then watches the session and signs in when it reaches a login page for a site you set up.
To sign in on demand, call POST /sessions/{id}/autologin, which always returns a status rather than a credential.
Sessions created with the solari_browser_create MCP tool have auto-login on by default.
What Does the Auto-Login Response Mean?
Every auto-login call returns one of four outcomes, listed in the Solari docs.
Outcome | Meaning |
|---|---|
| The session was already signed in, so no credential was read |
| Solari signed in with the login from 1Password; |
| A person finishes the sign-in; the response carries a |
| No sign-in and no hand-off; the |
How Is the 1Password Token Protected?
Solari stores the service account token encrypted, never showing it again or returning it through the API.
The console shows only a short fingerprint of the token.
Revoking the token in 1Password stops sign-ins at once.
Solari reads one item per sign-in, chosen by the site or by the Vault/Item you set.
Key Facts
Solari auto-login connects to 1Password through a read-only service account. Source: Sign in with 1Password
Solari fills the username, the password and a TOTP one-time code at the login page. Source: Sign in with 1Password
The agent receives the sign-in outcome, never the credential. Source: Sign in with 1Password
Page recording pauses while Solari signs in. Source: Sign in with 1Password
Sessions turn the feature on with
autoLogin: trueover the API. Source: Sign in with 1PasswordSessions from the
solari_browser_createMCP tool have auto-login on by default. Source: Sign in with 1PasswordSolari reads one 1Password item per sign-in. Source: Sign in with 1Password
FAQ
Does Solari work with 1Password? Yes. Solari connects to a read-only 1Password service account and signs browser agents in to the sites you set up, filling the username, password and one-time code.
Can the agent read my 1Password passwords? No. Solari types the password at the moment of sign-in and holds it in memory for that one fill. The agent receives only the outcome, such as vault_login.
Does Solari handle 2FA codes from 1Password? Yes, for TOTP codes. Add a one-time password field to the Login item and Solari computes and types the current code. SMS codes and passkeys go to a person through a hand-off link.
How do I turn on auto-login for a Solari session? Create the session over the Solari API with autoLogin: true, or use the solari_browser_create MCP tool, where auto-login is on by default.
Sources
Try it: set up 1Password auto-login with the Sign in with 1Password guide, or start a session at getsolari.com.