Skip to main content

Command Overview

beacon endpoint install configures the local endpoint agent, writes the OpenTelemetry Collector configuration, installs the launchd service, configures selected agent harnesses, and optionally adds Splunk HEC or Falcon LogScale HEC collector destinations.
Command syntax
By default, Beacon configures Claude Code and Codex CLI telemetry for local or customer-controlled runtime JSONL logs. Gemini CLI and VS Code Copilot telemetry are opt-in with the gemini and vscode harnesses. Claude Code can also use optional hook telemetry for richer lifecycle, subagent, permission, and tool detail; install the endpoint agent first, then add Claude hooks with beacon endpoint hooks install --harness claude. Codex runtime telemetry stays OTLP-based, but optional Codex hooks can trigger inventory heartbeats with beacon endpoint hooks install --harness codex. Beacon applies redaction, sanitization, truncation, and event-size limits before writing supported content fields. GitHub Copilot CLI and Factory Droid OTLP are managed through their launch environments, so Beacon validates their telemetry state but does not mutate shell profiles during install.

Flags

Examples

Install with the default per-user paths:
Install with the default per-user paths
Install without starting the launchd service:
Install without starting the launchd service
Configure only one harness:
Configure only one harness
Opt in Gemini CLI telemetry alongside the defaults:
Opt in Gemini CLI telemetry alongside the defaults
Configure VS Code Copilot telemetry:
Configure VS Code Copilot telemetry
Configure Devin CLI and Devin Desktop hooks alongside the default OTLP harnesses:
Configure Devin CLI and Devin Desktop hooks alongside the default OTLP harnesses
Include low-level runtime OTLP metrics that are filtered from JSONL by default:
Include low-level runtime OTLP metrics that are filtered from JSONL by default
Include raw Codex spans for troubleshooting:
Include raw Codex spans for troubleshooting
Install with system paths for a root-managed package or MDM deployment:
Install with system paths for a root-managed package or MDM deployment
Install and forward to CrowdStrike Falcon LogScale HEC:
Install and forward to CrowdStrike Falcon LogScale HEC
Configure Factory Droid’s OTLP endpoint through MDM or another customer-owned launch policy:
Configure Factory Droid's OTLP endpoint through MDM or another customer-owned launch policy
Configure GitHub Copilot CLI’s OTLP endpoint through MDM or another customer-owned launch policy:
Configure GitHub Copilot CLI's OTLP endpoint through MDM or another customer-owned launch policy
For richer hook telemetry, install runtime hooks after the endpoint configuration exists:
Install runtime hooks
Install Claude Code hooks at the user level:
Install Claude Code hooks at the user level
Install Grok Build hooks at the user level:
Install Grok Build hooks at the user level
Install Hermes Agent hooks at the user level:
Install Hermes Agent hooks at the user level
Hermes hooks write ~/.hermes/config.yaml and support user-level installs only. Project-level Grok Build hooks write ./.grok/hooks/beacon-endpoint.json and require /hooks-trust in Grok before they execute:
Install project-level Grok Build hooks
Production endpoint install is currently supported on macOS. Omit --system for the default non-root local install. GitHub Copilot CLI and Factory Droid OTLP use launch-environment settings rather than Beacon-managed shell-profile edits.

Endpoint status

Inspect collector health, runtime log state, harnesses, diagnostics, and forwarding readiness.

Runtime hooks

Install hook-based telemetry after the endpoint collector is configured.