Support Matrix
Beacon supports multiple runtime surfaces because each agent harness exposes telemetry differently. These integrations are grouped by where the agent runs and how telemetry is collected:- Local: Agent harnesses running on an endpoint write telemetry to Beacon’s local collector, hook adapter, plugin, or gateway path.
- CI: Ephemeral CI jobs use a temporary collector and write normalized runtime JSONL as a build artifact or upload target instead of installing a persistent endpoint service.
- Cloud: SDK integrations instrument agent applications that run in servers, serverless functions, workers, and hosted agent platforms.
Support matrix
Local Coding Agent Harnesses
| Agent harness | Collection path | Telemetry coverage |
|---|---|---|
| Antigravity CLI | Native hooks | Prompt, pre-tool, post-tool, stop, invocation, command, and file telemetry where Antigravity exposes hook payloads |
| Claude Code | Local OTLP export plus optional hooks | Prompt, command, tool, file, lifecycle, subagent, and permission telemetry where emitted through OTLP or hooks |
| Codex CLI | Local OTLP logs | Session, prompt, approval, and tool-result activity from Codex semantic logs |
| Cursor | Native hooks | Prompt, tool, shell command, MCP-like, approval, and file edit telemetry |
| Devin CLI | Native hooks | Session, prompt, pre-tool, post-tool, permission request, stop, session-end, approval, and file telemetry |
| Devin Desktop | Cascade/Windsurf hooks | Prompt, command, MCP tool, file read, and file write telemetry where Desktop exposes Cascade hook payloads |
| Factory Droid | OTLP HTTP plus optional hooks | Session, prompt, write/edit/create tool use, stop, session-end, and available OTLP telemetry |
| Gemini CLI | Opt-in local OTLP | Prompts, tool calls, MCP activity, file operations, and approval-related events emitted through OTLP |
| GitHub Copilot CLI | MDM-managed OTLP HTTP | Prompt, session, tool, and approval-like activity emitted through Copilot CLI spans |
| Grok Build | Native hooks | Session, prompt, pre-tool, post-tool, failed tool, stop, session-end, command, and file telemetry |
| OpenCode | Managed plugin hooks | Chat messages, session events, command execution, permission activity, diffs, and errors |
| VS Code | Copilot Chat OTel plus optional preview hooks | Copilot session, prompt, model, and tool activity through OTel; optional hooks for extra lifecycle and cross-agent detail |
Local Knowledge Worker Agent Harnesses
| Agent harness | Collection path | Telemetry coverage |
|---|---|---|
| Claude Cowork | Admin-configured OTLP | Prompt, command, tool, and file telemetry when emitted through Claude Cowork OTLP |
| Hermes Agent | Shell hooks | Prompt, observed tool, command, file, approval request and response, session lifecycle, and subagent stop telemetry |
| OpenClaw Gateway | Gateway-configured OTLP/HTTP | OTLP logs, traces, and metrics from the Gateway diagnostics plugin |
CI Harnesses
| Harness | Collection path | Telemetry coverage |
|---|---|---|
| Claude Code | Temporary local collector through beacon ci exec | Claude Code prompt, tool, command, file, and run context where emitted during the job |
Cloud Agent SDKs
| SDK | Collection path | Telemetry coverage |
|---|---|---|
| Anthropic | OpenLLMetry instrumentation through @asymptote/sdk | Supported Anthropic model call spans, errors, and OpenTelemetry attributes |
| Claude Agent SDK | Query wrapper through Observe.wrapClaudeAgentQuery() | Query root spans with Beacon-compatible prompt attributes |
| OpenAI | OpenLLMetry instrumentation through @asymptote/sdk | Supported OpenAI model call spans, errors, and OpenTelemetry attributes |
| Vercel AI SDK | Tracer handoff through experimental_telemetry | AI SDK model call and tool spans where telemetry is enabled |
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.
GitHub Copilot CLI and Factory Droid OTLP are controlled by launch environments. For Copilot CLI, set COPILOT_OTEL_ENABLED=true and OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318 through MDM or another customer-owned policy. For Factory Droid, set OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318. Beacon discovers both runtimes and validates the endpoint, but it does not mutate their shell profiles or launch environments.
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. Antigravity CLI, Claude Code, Cursor, Devin CLI, Devin Desktop, Factory, Grok Build, Hermes Agent, OpenCode, and optional VS Code 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
Agent harness integrations
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.