Opt-in persistent browser profiles for server-side agents to preserve login sessions

[betkyss]

Problem / use case

I use the T3 Code desktop app on macOS connected to a T3 server on a Mac mini. When an agent works with an authenticated website such as Notion through the built-in preview_* MCP tools, I repeatedly have to sign in again after the agent's browser tab is recreated.

Signing in to a regular browser tab using the Default profile does not make that login available to the agent's server-side tab. In Settings → Integrations → Browser, Agent browser access is enabled and Default is already the default profile. There does not appear to be a setting to let server-side agent tabs use that persistent profile.

Reusing the same tabId helps while its context is alive, but it does not provide persistent authentication after the context is destroyed or the server restarts. A skill instructing the agent to use Default cannot solve this because preview_open does not expose a profile selector in this version.

Requested feature

Please add an opt-in setting for agent browser session persistence, for example:

• Isolated / temporary — retain the current behavior.
• Use a persistent browser profile — select Default or a dedicated profile for agent browsing.

When explicitly enabled, user and agent tabs on the same T3 server should be able to use the selected profile's cookies and site storage, while keeping their tabs and control ownership separate. New agent tabs and later agent sessions should reuse that profile, and persistent login data should survive normal server restarts, subject to the website's own session expiration/revocation rules.

The UI should clearly distinguish a temporary agent context from a persistent profile. Sharing should be explicitly chosen, since agents using that profile would have access to its signed-in accounts. Incognito and other profiles should remain isolated.

I am requesting profile reuse on the same server, not automatic cookie synchronization between different machines.

Implementation context

Version inspected: 0.0.46-nightly.20261008.2833, macOS desktop + macOS remote server.

In the code associated with this desktop build (a6ec88f7a716), and in the installed server binary:

• ServerBrowser.ts marks a server-hosted agent tab as isolatedContext when it has an automationOwner and is not attached to a desktop page, then passes a tab-specific isolation key to contextFor.
• ServerBrowserContexts.ts uses browser.newContext(...) when an isolation key is supplied, whereas ordinary persistent profiles use chromium.launchPersistentContext(...).

This appears to be intentional isolation, so I am filing this as a request for an explicit persistent-profile option rather than claiming all browser cookies are failing to save.

Related discussions

• Per-project default browser profile (so agent-opened tabs use the right profile) #13255 — per-project default browser profile and profile selection for agent-opened tabs.
• Browser profiles: share a custom profile's cookies across all environments #16180 — sharing custom-profile cookies across environments.

This request focuses on the separate issue of temporary server-side agent contexts losing authentication when their tabs/contexts are recreated.