Grok Bot adds 1Password approvals for browser logins

xAI has added 1Password support to Grok Bot, its browser-driving AI agent. Users can share selected credentials, approve individual login fills, and let the Bot continue working through an authenticated cloud browser session.

The integration gives the agent access to websites that lack an API or dedicated connector while avoiding a bulk export of the user’s password vault. The browser still submits each credential to its destination, and the resulting session may remain active after approval.

Why logins stall browser agents

Each Grok Bot runs on a persistent cloud computer and operates software through the user interface. That approach lets it work with internal tools, legacy dashboards, and other browser-based services that offer no machine-readable integration.

Authentication creates the main obstacle. A browser agent needs a valid user session, which previously required users to enter credentials in the remote browser or arrange a manual handoff. The 1Password integration introduces a per-fill approval process for that step.

API and Model Context Protocol connectors usually provide more stable automation, narrower permissions, and structured data. Browser control covers the remaining services, but it depends on page layouts, session state, and the same access controls encountered by a human user.

One fill at a time

The new workflow limits credential access to selected vaults or items and requires approval when the Bot reaches a login form:

1. The user shares a specific 1Password vault or item with the Bot.
2. The Bot encounters a login screen and requests the matching credential.
3. The user approves that fill.
4. 1Password inserts the credential into the Bot’s cloud browser session.
5. The authenticated session persists until the site expires it, the user signs out, or another control invalidates it.

Multi-factor authentication, CAPTCHAs, and other human checks may still pause the workflow. Grok Bot can hand over control of the remote browser when a site requires direct user input or confirmation.

A login becomes a reusable session

A saved 1Password login can provide the starting point for recurring browser work, subject to the destination site’s automation rules. Possible targets include internal admin panels, vendor portals, analytics dashboards, support systems, and consumer services without a suitable connector.

An early hands-on test used Freshdesk without installing a native integration. The tester opened Freshdesk in the virtual browser, transferred the login from 1Password, and authenticated the session. The support Bot could then check for new tickets every 15 minutes using that existing session.

Credential approval grants more than a single page load. An active session may let the Bot perform every action available to that website account, so account permissions and session duration determine the practical scope of access.

Shared sessions set the boundary

Grok Bot uses Cursor authentication and account data settings. Bots associated with the same account also share one cloud computer, including its browser sessions and saved login state.

Separate Bots therefore do not provide account-level isolation. A login created for one Bot may remain available to another Bot running on the same cloud computer. Teams that need stronger separation should use distinct accounts, least-privilege website roles, and narrowly scoped 1Password sharing.

xAI also warns that browser workflows can fail when interfaces change, sessions expire, or CAPTCHAs appear. A first-party API or MCP connector remains the preferred option when one exists because it avoids many of those browser-specific failure modes.

Paid plans gate the rollout

Grok Bot requires a qualifying paid plan. The published access options include Cursor Ultra at $200 per month, Cursor Premium Teams at $120 per seat per month, and existing SuperGrok Heavy subscriptions.

The 1Password integration is rolling out within the existing product. Eligible users can configure it by sharing an appropriate vault or item from 1Password. The official FAQ explains the approval rules, account settings, and shared-computer model.

Using an established password manager as the credential source gives Grok Bot a controlled route into browser-only software. Its security depends on careful vault scoping, limited website permissions, and recognition that an approved login can create a reusable session for every Bot sharing that cloud computer.