Documentation Index
Fetch the complete documentation index at: https://docs.asymptotelabs.ai/llms.txt
Use this file to discover all available pages before exploring further.
Supported Runtimes
Beacon supports multiple runtime surfaces because each AI agent runtime exposes telemetry differently. This page expands the Supported Surfaces overview with per-runtime coverage details.Coding agent feature matrix
| Coding agent | Collection path | Discovery and status | Endpoint install support | Hook support | MDM support | Prompt telemetry | Command, tool, and file telemetry | Local JSONL and dashboard | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Claude Code | Local OTLP export to Beacon’s localhost collector | Detected through the claude executable and Claude settings paths | beacon endpoint install configures Claude telemetry | Not currently hook-based | Supported through system-mode package or MDM-managed settings | Supported when retention is full or redacted | Supported when emitted through OTLP | Supported | Uses Claude settings to enable telemetry and point OTLP to localhost. |
| Codex CLI | Local OTLP logs, with optional debug spans | Detected through the codex executable and ~/.codex/config.toml | beacon endpoint install writes Codex OTLP exporter tables | Not currently hook-based | Supported through system-mode package or MDM-managed config | Configurable through content retention | Supported when emitted through Codex semantic logs; raw Codex spans are available with --include-codex-spans for troubleshooting | Supported | Beacon keeps Codex timelines focused on session, prompt, approval, and tool-result activity. |
| Gemini CLI | Opt-in local OTLP logs, traces, and metrics | Detected through the gemini executable and ~/.gemini/settings.json | beacon endpoint install --harness claude,codex,gemini writes Gemini telemetry settings | Not currently hook-based | Supported through system-mode package or MDM-managed config when gemini is included in the harness list | Supported when retention is full or redacted | Supported for prompts, tool calls, MCP activity, file operations, and approval-related events emitted through OTLP | Supported | Beacon writes ~/.gemini/settings.json telemetry settings with target: local, OTLP gRPC, collector mode, and no outfile. |
| OpenCode | Managed local plugin through beacon-hooks | Detected through the opencode executable or ~/.config/opencode, then checked for Beacon plugin configuration | Endpoint install prepares shared endpoint config and log paths | beacon endpoint hooks install --harness opencode | Supported for the endpoint agent; OpenCode plugins are installed separately in the logged-in user’s context | Supported through chat.message hooks | Supported for chat messages, session events, command execution, permission activity, diffs, and errors where OpenCode exposes payloads | Supported | Beacon installs an owned plugin at ~/.config/opencode/plugins/beacon.ts or ./.opencode/plugins/beacon.ts. |
| Devin | Native hook payloads through beacon-hooks | Detected through the devin executable, ~/.config/devin, or ./.devin, then checked for Beacon hook configuration | Endpoint install prepares shared endpoint config and log paths | beacon endpoint hooks install --harness devin | Supported for the endpoint agent; Devin hooks are installed separately in the logged-in user’s context or project context | Supported through UserPromptSubmit hooks | Supported for session, prompt, pre-tool, post-tool, permission request, stop, session-end, approval, and file telemetry where Devin exposes payloads | Supported | Beacon writes user hooks to ~/.config/devin/config.json or project hooks to ./.devin/hooks.v1.json. |
| Factory Droid | OTLP HTTP launch environment plus optional hooks | Detected through the droid executable and validated against OTEL_TELEMETRY_ENDPOINT | Endpoint install prepares the collector; Factory’s launch environment is managed by MDM or customer policy | beacon endpoint hooks install --harness factory or --harness droid | Supported for the endpoint agent; Factory launch environment and user/project hooks are managed in the user’s Droid context | Supported through UserPromptSubmit hooks | Supported for session, write/edit/create tool use, stop, session-end, and available OTLP telemetry | Supported | Beacon validates Factory OTLP state but does not mutate shell profiles for Droid. |
| Cursor | Native hook payloads through beacon-hooks | Detected through the Cursor binary or ~/.cursor, then checked for Beacon hook configuration | Endpoint install prepares shared endpoint config and log paths | beacon endpoint hooks install --harness cursor | Supported for the endpoint agent; Cursor hooks are installed separately in the logged-in user’s context | Supported through beforeSubmitPrompt hooks | Supported for tool, shell command, MCP-like, approval, and file edit payloads where Cursor exposes them | Supported | Restart Cursor after installing or removing hooks. |
| Claude Cowork | Admin-configured OTLP from Anthropic’s service | Treated as an admin-configured source and validated with Claude Cowork commands | Configured in Claude organization settings, not local endpoint install | Not hook-based | Uses a durable customer-managed HTTPS collector endpoint rather than local MDM hook config | Supported when emitted through Claude Cowork OTLP | Supported when emitted through Claude Cowork OTLP | Supported after events reach the collector | Production Cowork telemetry should use a public HTTPS collector endpoint, not a laptop or ngrok tunnel. |
| OpenClaw Gateway | Gateway-configured OTLP/HTTP export | Validated by scanning the endpoint runtime log for OpenClaw-derived events | Configured in OpenClaw Gateway with the diagnostics-otel plugin, not local endpoint install | Not hook-based | Supported for the endpoint agent; Gateway diagnostics configuration is managed in OpenClaw | Disabled by default unless OpenClaw captureContent settings are explicitly enabled | Supported for OTLP logs, traces, and metrics emitted by the Gateway diagnostics plugin | Supported after events reach the collector | Beacon prints local OTLP/HTTP Gateway config and validates observed OpenClaw events. |
Runtime support notes
- Claude Code: configured to export OpenTelemetry to Beacon’s localhost collector. Prompt content is exported when content retention is set to
fullorredacted. - Codex CLI: configured through
~/.codex/config.tomlto export OpenTelemetry logs to Beacon’s localhost collector. Beacon uses Codex semantic logs for session, prompt, approval, and tool-result events, suppresses high-volume Codex spans and metrics by default, and keeps prompt text out of metadata-only retention. Use--include-codex-spansduring install or repair only when you need raw Codex spans for troubleshooting. - Gemini CLI: opt-in through the
geminiendpoint harness. Beacon writes local OTLP settings to~/.gemini/settings.json; project settings orGEMINI_TELEMETRY_*environment variables may override that user config. - OpenCode: configured through a managed local plugin that invokes Beacon’s hook adapter for chat, session, command, permission, diff, and error events where payloads are available.
- Devin: configured through hook entries in
~/.config/devin/config.jsonfor user-level installs or./.devin/hooks.v1.jsonfor project-level installs. Beacon preserves unrelated Devin settings and non-Beacon hooks. - Factory Droid: discovered through the
droidexecutable and validated through the effectiveOTEL_TELEMETRY_ENDPOINT. Factory can send OTLP HTTP to the local collector, and Factory hooks can emit session, prompt, write/edit/create tool, stop, and session-end events where payloads are available. - Cursor: configured through hooks that invoke the embedded
beacon-hooksadapter for session, prompt, tool, command, MCP-like, approval, and file edit telemetry where payloads are available. - Claude Cowork: configured in Claude organization settings and validated with Beacon’s Claude Cowork integration commands.
- OpenClaw Gateway: configured in OpenClaw Gateway with the
diagnostics-otelplugin. Beacon prints a local OTLP/HTTP config and validates whether OpenClaw-derived events have reached the runtime log.
Deployment notes
For MDM deployments, use the signed and notarized macOS.pkg so endpoint events land in /var/log/beacon-agent/runtime.jsonl. The package installs Beacon under /opt/beacon, creates system endpoint configuration, loads the local collector LaunchDaemon, and supports Jamf Pro, Fleet, or another macOS MDM.
Gemini CLI telemetry is opt-in. In enterprise rollouts, add gemini to the endpoint harness list, for example claude,codex,gemini, when you want Beacon to manage ~/.gemini/settings.json for local OTLP collection. Factory Droid OTLP is controlled by Droid’s launch environment. Set OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318 through MDM or another customer-owned launch policy. Beacon discovers Droid and validates the endpoint, but it does not mutate shell profiles. OpenClaw Gateway is configured in OpenClaw rather than by endpoint install; use beacon endpoint integrations openclaw to print local Gateway OTLP settings and validate events. Cursor, Devin, Factory, and OpenCode hooks are installed separately in the logged-in user’s context when you need richer hook telemetry.
If a system collector is running while the CLI is reading the default per-user log, beacon endpoint status and the local dashboard surface a runtime-log source warning so you can tell where OTLP events are being written.
Related
Supported surfaces
Return to the support overview.
Runtime integrations
See how Beacon discovers and configures each runtime.
Hooks
Install, inspect, and uninstall runtime hook integrations.
MDM deployment
Deploy Beacon through Jamf Pro, Fleet, or another macOS MDM.