Browser session persistence for Cursor's agent, free with the built-in browser, and when Hronaut is worth paying for
Cursor's built-in browser already keeps the agent signed in between sessions, per workspace. Here is how that works, where it stops, and the cases where a separate browser app like Hronaut earns its $4 a month.
You want Cursor's agent to test a page behind a login without signing in every time. Good news first: Cursor already does this for free. This post shows what it keeps, where it stops, and when a separate browser is worth it. I build Hronaut, the paid option at the end, so the free route comes first.
The free way: Cursor's built-in browser
Cursor ships a browser the agent can drive with no setup. It opens in a separate window or as a pane inside Cursor, and the agent sees its console and network log. Ask for it in chat:
@browser Open http://localhost:3000/login, wait for me to sign in,
then open Settings and report any console errors.
Cursor's documentation says browser state persists between agent sessions, per workspace:
- Cookies, so authentication and session data stay available.
- localStorage and sessionStorage.
- IndexedDB.
Each workspace has its own browser context, so two projects do not share cookies or storage. Sign in once in a project, and the next agent session in that project is still signed in.
If you work in Cursor, test one account per project, and only Cursor's agent needs the browser, this is enough. Persistence does not require Hronaut.
A second free option: Playwright MCP
If you prefer an external browser, add Microsoft's open-source Playwright MCP in Cursor Settings › MCP › Add new MCP Server, as a command server running npx @playwright/mcp@latest. It also keeps a persistent profile by default, and --user-data-dir chooses where.
Where the free routes stop
- One browser context per workspace. The built-in browser keeps one set of cookies per project. Checking the same app as an admin and as a regular member at the same time, or keeping two client accounts apart inside one project, needs a second context you set up yourself.
- The browser belongs to Cursor. Its sign-ins are not available to Claude Code, Codex or another agent working on the same project, and its tabs live with the Cursor window.
- No pause. You can watch the agent, but nothing stops its next action while you type a password or a 2FA code.
When Hronaut is worth it
Hronaut is a desktop browser that runs as its own app. Cursor connects to it as an MCP server, and so can Claude Code, Codex and other clients.
- Several named workspaces per project. Each has its own cookies and sign-ins, so
staging-adminandstaging-membercan be open side by side and the agent can compare what each one sees. - One sign-in, several agents. A workspace you signed in to from Cursor can be resumed from Claude Code or Codex with its ID and private resume key.
- The browser outlives the editor. Close Cursor and the workspace stays open with its tabs and page state.
- Pause and take over. Pause agent access, sign in or pass 2FA yourself in the same tab, and hand it back. The agent can ask for your attention on a tab when it reaches a human-only step.
It costs $4 a month or $24 a year per named user after a 10-day trial, which needs no card and never charges you. It is one more desktop app to keep updated, and it drives Chromium only.
Try it
Install Hronaut from the download page and add it to Cursor with the install link or configuration on the Cursor setup page. Then ask:
Create Hronaut workspaces named staging-admin and staging-member.
Open https://staging.example.com in each and ask for my attention
so I can sign in as an admin and as a member. Then open the
Billing page in both and tell me what each one shows.
The Claude Code version of this post covers Playwright MCP's profile in more detail, and the Codex version covers Codex's built-in browser.
Sources: Cursor Browser documentation (session persistence, per-workspace isolation, pane or window), Playwright MCP README (Cursor setup, persistent profile, --user-data-dir), Hronaut README (workspaces, pause and takeover, resume), hronaut.dev/pricing, Cursor setup guide.
Written with the help of AI.