Beeuni in Chrome

Let a session use your browser, with access you choose.

Beeuni in Chrome lets a session open pages and use sites where you are already signed in. It is experimental and appears only when the deployment administrator has configured a Beeuni extension. There is no public Chrome Web Store listing yet. Ask your administrator for the approved extension package and installation instructions.

Connect a browser

Install the package your administrator provides in the browser profile you want to use.
Open Settings → Beeuni in Chrome in Beeuni and choose Connect. Sign in with your own Beeuni account when the extension asks.
Choose the browser’s access mode and tab scope. Keep the browser open while the session uses it.

Each browser connection belongs to the person who signs in. Connecting it does not create a shared connector account: other members do not get your browser in their browser list. You do not need to paste site passwords or cookies into Beeuni. The agent can still read content and perform actions on permitted tabs using your site’s current login. Grant access only to the tabs the task needs.

Choose access

Ask first: an attachment request shows an approval in Chrome. Allow this session, allow eligible sessions in this project, or deny it.
Without asking: eligible sessions can attach without another prompt.
Off: new attachments are refused.

All tabs is the default scope and exposes tabs across browser windows. Only tabs it opens limits the agent to its session’s tabs. Chrome’s built-in pages, extension pages, and the Chrome Web Store are not accessible.

Work and stop

Ask the agent to use your connected browser. Its tabs appear in a session group where the browser supports groups. Take over pauses agent input; Stop ends that attachment. Do not ask the agent to retry after Stop unless you want to approve access again.

In a session terminal, the equivalent commands are:

beeuni chrome use
beeuni chrome status
beeuni chrome release

Release ends the attachment; it does not sign you out of websites. Disconnect in the browser settings revokes the Beeuni browser connection. To use it again, reconnect.

Deployment configuration

Administrators must use their own Beeuni extension ID:

API: set BEEUNI_CHROME_ENABLED=true and BEEUNI_CHROME_EXTENSION_ID.
Web: set NEXT_PUBLIC_BEEUNI_EXTENSION_ID to the same extension ID and rebuild.

Apply the Chrome database migration and deploy the updated API, web app, and session runtime with the Chrome bridge. Update the sandbox image if it still contains an older runtime. An environment switch alone does not add the bridge to an old image. The project must also have the Chrome feature enabled. Without a valid configured extension ID, the platform keeps the feature off.