Agentbeamdocs

Start here

MDM / Getting startedDevice managementOne place to understand your Apple and Windows fleet, deliver configuration, and request device actions.MDM / Getting startedSet up your workspaceRequest MDM access, check platform readiness, and get your first managed device into inventory.Agent CLI / Getting startedAgent CLI overviewUnderstand agent activity locally, scan the files your assistants use, and connect shared workspace controls when needed.Agent CLI / Getting startedCLI quickstartInstall Beam, capture a first event, and open your local activity dashboard.Agent CLI / Getting startedConnect a workspacePair your machine through the browser or an enrollment code, then verify identity and policy synchronization.
↑ ↓ to navigate · Enter to openEsc to close
Website Open dashboard
Agent CLI/Browser extension
Browser extension

Install the extension

Build and load Beam Sentinel from a reviewed checkout, then verify site access and local protection.

On this page

This guide uses the repository's unpacked extension build. It requires Bun to build and Chrome 111 or later, as declared in the manifest. No Beam account or local collector is required.

Build a reviewed version

From the Beam repository root:

Code
bun run --cwd chrome-apps/beam-sentinel build

The build writes the extension to chrome-apps/beam-sentinel/dist. Review the release and source before loading it into your daily browser profile. The source folder alone is not the built extension artifact.

Load in Chrome

  1. Open chrome://extensions.
  2. Enable Developer mode.
  3. Choose Load unpacked.
  4. Select chrome-apps/beam-sentinel/dist.
  5. Pin Beam Sentinel using Chrome's extension menu if you want quick access to its popup.
  6. Open or reload a supported assistant page so its content script is active.

Chrome's extensions page is a browser-internal address; enter it in the address bar. Your organization's managed browser policy may control whether unpacked extensions are allowed.

Verify protection

Open the toolbar popup and confirm Protection on. Check that Chrome permits the extension on the intended site. Send a harmless message and inspect the local recent-actions list.

A popup opening successfully does not prove the current website composer is intercepted. Verify the actual supported send flow, including the composer type you use. New tabs, changed host permissions, or a site redesign can require another check.

Update a local build

Review the new source, rebuild the extension, then use Reload on Chrome's extensions page. Reload existing assistant tabs as well so they use the current content script. An unpacked install does not automatically follow repository changes.

Pause or remove

The popup switch pauses protection. Clear removes the locally stored recent decision list. Neither action deletes conversation content already submitted to an AI website.

To remove the extension, use Remove on chrome://extensions. This is separate from beam uninstall, which manages the CLI installation. If the browser is managed by your organization, use its approved extension-removal process.

Keep exploring

Explore the docs