Skip to main content

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.

​
Runtime Integrations

Beacon supports multiple runtime surfaces because each AI agent runtime exposes telemetry differently. Claude Code, Codex CLI, Gemini CLI, Claude Cowork, and OpenClaw Gateway use OpenTelemetry paths. Cursor, Devin, OpenCode, and Factory Droid can use the embedded beacon-hooks adapter where hook payloads expose richer runtime activity.

​
Discovery and status

beacon endpoint discover checks which supported AI runtimes are present and whether their telemetry is configured.
RuntimeHow Beacon discovers or validates it
Claude CodeLooks for the claude executable and Claude settings paths
Codex CLILooks for the codex executable and ~/.codex/config.toml
Gemini CLILooks for the gemini executable and ~/.gemini/settings.json
OpenCodeLooks for the opencode executable or ~/.config/opencode, then checks the managed Beacon plugin
DevinLooks for the devin executable, ~/.config/devin, or ./.devin, then checks Beacon hook configuration
Factory DroidLooks for the droid executable and validates OTEL_TELEMETRY_ENDPOINT in the effective launch environment
CursorLooks for the Cursor binary or ~/.cursor, then checks Beacon hook configuration
Claude CoworkTreats it as an admin-configured OTLP source because telemetry is enabled in Claude organization settings
OpenClaw GatewayValidates observed OpenClaw-derived events in the runtime log after Gateway diagnostics are configured

​
Install-time configuration

During install, Beacon configures the runtime surfaces it can safely manage:
  • Claude Code and Codex CLI are pointed at the local OTLP collector.
  • Codex CLI receives structured OTLP exporter tables in ~/.codex/config.toml; Beacon also sets log_user_prompt = false and sends logs, traces, and metrics to the local collector.
  • Gemini CLI can be opted in with --harness gemini; Beacon writes local OTLP settings to ~/.gemini/settings.json, sets target to local, uses OTLP gRPC, enables the collector, and removes outfile so telemetry flows to Beacon.
  • Factory Droid’s OTLP endpoint stays under Droid’s launch environment, commonly managed through MDM or another customer-owned policy.
  • OpenClaw Gateway is configured in OpenClaw with the diagnostics-otel plugin; Beacon prints local OTLP/HTTP setup guidance and validates observed events.
  • Cursor, Devin, Factory, and OpenCode hooks are installed separately with beacon endpoint hooks, because hooks are per-user or per-project runtime configuration rather than base collector service configuration.

​
Integration paths

RuntimeCollection pathNotes
Claude CodeLocal OTLP export to Beacon’s localhost collectorUses Claude settings to enable telemetry and point OTLP to localhost.
Codex CLILocal OTLP logs, traces, and metricsBeacon writes structured Codex OTLP config and filters noisy internal transport spans.
Gemini CLIOpt-in local OTLP logs, traces, and metricsBeacon writes Gemini telemetry settings and maps Gemini prompts, tool calls, MCP activity, file operations, and approval events into endpoint events.
OpenCodeManaged local plugin through beacon-hooksPlugin invokes Beacon for chat, session, command, permission, diff, and error events where payloads are available.
DevinNative hook payloads through beacon-hooksHooks emit session, prompt, pre-tool, post-tool, permission request, stop, session-end, approval, and file telemetry where Devin exposes payloads.
Factory DroidOTLP HTTP launch environment plus optional hooksBeacon validates Factory OTLP state but does not mutate shell profiles for Droid.
CursorNative hook payloads through beacon-hooksHooks emit session, prompt, tool, command, MCP-like, approval, and file edit telemetry where Cursor exposes payloads.
Claude CoworkAdmin-configured OTLP from Anthropic’s serviceProduction Cowork telemetry should use a durable customer-managed HTTPS collector endpoint.
OpenClaw GatewayGateway-configured OTLP/HTTP exportBeacon prints Gateway diagnostics settings and validates OpenClaw-derived events in the runtime log.

​
Hook telemetry

Cursor, Devin, Factory, and OpenCode hooks cover activity that is better represented as runtime events than generic OTLP spans.
  • Cursor records session lifecycle, prompt submission, tool invocation, shell command execution, MCP-like tool activity, approval decisions, and file edits where payloads are available.
  • Devin records session lifecycle, prompt submission, pre-tool and post-tool activity, permission requests, stop events, session-end events, approvals, and file telemetry where payloads are available.
  • Factory records session start and end, prompt submission, write/edit/create tool use, stop events, and related file activity where payloads are available.
  • OpenCode records chat messages, session events, command execution, permission activity, diffs, and errors where payloads are available.
Hook events include metadata such as file path, operation, language, diff hash, and diff byte count. Raw diffs follow the configured content-retention mode and are excluded when you choose metadata.

Beacon architecture

Return to the architecture overview.

Telemetry pipeline

Follow runtime signals through collection, normalization, storage, and forwarding.

Supported runtimes

Compare runtime support in the detailed feature matrix.

Hooks

Install, inspect, and uninstall runtime hook integrations.