Spaces and logins

Use a private space for temporary browsing. Use a named saved space when you want to keep a login. Each agent gets a separate browser context.

Choose a space

{"name":"space","arguments":{"action":"use","name":"work"}}

A saved name uses letters, digits, - or _, up to 40 characters. Switching spaces closes that agent’s tabs and opens a blank tab. Only one agent can use a saved space at a time. List spaces before choosing one:

{"name":"space","arguments":{"action":"list"}}

Return to a new private space with space and {"action":"leave"}.

Sign in by hand

Ask the agent to request a human check. Enter the credentials in the controlled page, then return the page to the agent. While you control it, the agent cannot read it or take screenshots. Do not paste credentials into chat.

What is saved

Saved spaces keep cookies, local storage and IndexedDB for visited top-level HTTP(S) origins. IndexedDB is bounded to 4 MiB per origin and 16 MiB per space; unsupported values or failed capture/restore report an error. They do not save sessionStorage, Cache Storage or service workers. Some sites will ask you to sign in again. Space data is encrypted with the vault. The space key uses the system keychain, or an explicitly configured owner-only key file. A denied or locked keychain is not silently replaced with a new file key.

Private browser state is discarded on close. Private recordings are removed on close and reconciled on restart after a crash. Files you explicitly download or export can have a separate lifetime; review and delete those files yourself. Private browsing does not erase data already sent to websites or to your agent’s provider.

Remove a login

Close the agent using the space, then delete the saved space in the window. You cannot wipe a space while another agent uses it. Cookie imports and exports need human approval. Treat an exported cookie file like a password; keep it out of chat and source control.