Beacon Files

Agent Beacon browser collector (browser-extension/) for Chromium browsers, in two forms built from the same bytes:

• agent-beacon-browser-extension-0.2.0-chrome.crx: the signed build for managed fleets. Chrome policy force-installs it from the update feed, and installed copies update themselves from it. Extension ID omjgmakjpomopmmpdgmjbfojhbgdgijc, update URL https://github.com/Asymptote-Labs/agent-beacon/releases/download/ext-updates/updates.xml. See https://docs.beacon.sh/runtimes/browser-extension-chrome-policy.
• agent-beacon-browser-extension-0.2.0-chrome.zip: the unpacked build, for development and single machines. Unzip it, open the extensions page (chrome://extensions, edge://extensions, ...), turn on Developer mode, and choose Load unpacked.

Requires a running Beacon endpoint: the extension POSTs OTLP GenAI logs to http://127.0.0.1:4318/v1/logs.

Retention defaults to full, meaning complete prompt and response text from claude.ai and chatgpt.com is written to the local runtime log. Admins can lock retention and the other settings through Chrome policy; on a single machine, change it in the extension's options page before enabling it where you use those sites personally.

Verify either file against the .sha256 published beside it. Chrome also checks the CRX signature against the extension ID when it installs it:

shasum -a 256 -c agent-beacon-browser-extension-0.2.0-chrome.zip.sha256
shasum -a 256 -c agent-beacon-browser-extension-0.2.0-chrome.crx.sha256