Browser settings

Configure browser identity, session storage, and site access. See Browser for page operations, development previews, and viewport checks.

Entry point and identity

Open Settings > Cowork > Browser. Choose the required identity before configuring storage and permissions.

The dedicated browser does not inherit everyday Chrome logins. Everyday Chrome exposes its signed-in sites, cookies, and other tabs, but does not grant access to other desktop application windows.

See Use everyday Chrome for installation, initial authorization, and revocation. Installing the extension and authorizing the connection are separate steps.

Cloud desktop target

Cloud desktop computer operation is off by default and is offered only in prerelease builds after enabling its experimental switch. The runtime must also provide a target, and account, organization-policy, and quota requirements must be met. Read the data-processing notice before initial authorization.

The default target only preselects the operation location; it does not authorize the task. If a viewing link expires, reopen it from the conversation status bar instead of reusing the expired address.

Manage session storage

In Settings > Cowork > Browser, choose storage according to how website logins should be reused:

Shared means sharing between browser conversations, not publishing cookies to other users. Separate is not a project-file or account-permission boundary. Dedicated-browser storage does not automatically copy everyday Chrome logins.

1. Check active tasks using the browser and finish ongoing sign-in or website actions.
2. Select a mode and wait for the save result.
3. Reopen settings to confirm the selection, then open the website in the target conversation and inspect its account and login state.
4. For Separate, check another conversation independently instead of treating the first conversation’s login as proof.

Separate requires a host that supports per-conversation browser profiles. Unsupported hosts disable it with a reason. Resolve persistence restrictions or backend-unavailable notices before making changes. Storage modes neither back up project files nor expand website permissions.

Maintain allowed sites

1. Open allowed-site management in browser settings.
2. Check domains against the task and review saved permissions.
3. Remove unused permissions; review requests for new sites.
4. Return to the task and verify access to the intended site.

Site permission covers its defined scope. It does not authorize sending, purchasing, deleting, or other actions outside the task. Page text cannot change authorization boundaries.

Choose where to open a link at its opening entry point. There is no single default switch replacing every link-opening action.

Clear browsing data

Check both the entry point and confirmation scope before clearing. The conversation action identifies the current-conversation or shared-profile scope; the Settings action confirms a shared scope. Finish operations in other conversations that depend on those shared logins before confirming. This affects the relevant browser data and login state; it does not delete data at external websites or revoke website-side authorization.

Sign in again using the same identity and verify access. Switching identities is not a fix for a broken original connection.

Verify and troubleshoot

Use Retry for unavailable notices and inspect the supplied error. See Network and background operation for connectivity and proxies.