Workspace browser data

Understand the workspace extension's browser events, metadata defaults, text collection controls, and rollout requirements.

On this page

The workspace browser extension, Agentbeam, is our main extension with every feature. It is a separate implementation from free Beam Sentinel: it connects a browser profile to a workspace, applies the workspace's AI data policy to supported pages, and reports browser interactions. Install it from the Chrome Web Store (version 0.2.4 as of October 25, 2026). It needs an Agentbeam workspace and an enterprise entitlement, and deployment to your own browsers still needs a pilot you verify.

Choose the right extension

Free Beam Sentinel checks supported prompts locally, requires no Beam sign-in, and retains a small redacted history in the browser. It does not upload that history to a workspace.

The workspace extension uses device enrollment, membership checks, and an enterprise entitlement. Signing in alone does not enable tracking. Each browser must be explicitly connected, and collection stops when the implementation detects expired policy or lost access. It has a separate device identity from a CLI on your laptop or Raspberry Pi.

Understand the recorded data

Browser surfaceWhat a record means
Supported provider visitProvider origin, local random session identifier, and timestamp; not whole-browser history
Prompt submissionA submission attempt, text length, local decision, and finding categories; not confirmed delivery
Composer pasteA paste interaction, length, and findings; not a global clipboard log
Attachment selection, paste, or dropCoarse type and size for supported file paths; file names and bytes are not read
Visible response changesAn observed response and its length; a pause in streaming is not proof of completion
Copy, regenerate, stop, or shareA supported interface interaction; not proof of the provider's resulting action

The extension's manifest covers ChatGPT, Claude, Gemini, Perplexity, Microsoft Copilot, Grok, DeepSeek, Meta AI, Mistral and Qwen. Existing conversations are not backfilled. Provider layout changes can affect capture, and a browser interaction cannot reliably identify whether a human or automation performed it.

Control text collection

Metadata only is the default. Workspace managers can opt into up to 4,000 characters of heuristically redacted prompt, response, or paste text under Policies → Enterprise browser. The extension displays the active collection setting. Known secret patterns are masked, but arbitrary sensitive prose can remain; redaction is not semantic anonymization.

Browser controls use their own provider, attachment, mode, and collection settings. The CLI policy presets configure agent command/tool restrictions; they do not automatically become browser rules. Member overrides cannot enable browser text collection or weaken the workspace browser controls.

Interpret delivery and protection

Browser events use bounded local queues with retry and visible loss accounting. Records may be dropped or expire, so the dashboard is not a lossless transcript. API identity comes from the enrolled device credential, and the server checks membership and entitlement again before accepting records.

Protection operates on supported page interactions. It does not cover arbitrary API calls, native AI apps, every browser network path, or commands that execute on a remote computer. Combine browser records with CLI capture and verify each surface independently during a pilot rollout. Avoid running both extensions in the same profile during that pilot because both can review prompts.

Set this up with your coding agent

Install the agentbeam-setup skill for Claude Code, Codex, Cursor, Gemini CLI, OpenCode and Copilot, then ask your agent to set up AgentBeam on this machine. Beam scans the skill before it installs.

npx -y @agent-beam/beam add skill agentbeam-setup -g --all-agents
Docs
Esc

Jump to a section

Actions