Install Beacon
Install Beacon
Example output
Example output
beacon version output
Configure endpoint telemetry
For most individual developer setups, continue with the default per-user endpoint install:Configure endpoint telemetry
127.0.0.1. Add Gemini when you want Beacon to manage Gemini OTLP settings too:
Include Gemini telemetry
Production endpoint install is currently supported on macOS. The default mode uses per-user paths; use
--system as root for package or MDM deployments.runtime.jsonl or sent through configured destinations, Beacon applies redaction, sanitization, truncation, and event-size limits.
Beacon filters generic process/runtime OTLP metrics, Copilot CLI and OpenClaw operational metrics, and high-volume Codex spans out of the local JSONL log by default. Use --include-runtime-metrics or --include-codex-spans only when troubleshooting.
Upgrade Beacon
Use the standard Homebrew upgrade flow, then reapply endpoint configuration if needed:Upgrade Beacon
beacon endpoint repair reapplies managed service files, collector configuration, harness telemetry settings, and forwarding destinations while preserving runtime logs. On v0.0.43 or newer, use beacon endpoint doctor --fix when you only need supported health-check drift remediated without a full repair.
Related
Hosting Options
Choose between Asymptote Cloud and the open-source local Agent Beacon path.
Paths
Review files, logs, collector config, ports, and hook locations.
Endpoint command reference
Review install, status, repair, and uninstall commands.
Endpoint repair
Reapply service files and telemetry configuration.
Manual archives
Install from platform archives or build the CLI from source.

