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.

​

Claude Code

Beacon supports Claude Code through local OpenTelemetry export to Beacon’s localhost collector.

​

Prerequisites

Before enabling Claude Code telemetry, make sure:

• Claude Code is installed and available as the claude executable for the user or managed endpoint.
• beacon endpoint install has run so the local collector, endpoint config, and runtime log path exist.
• The install includes the claude harness, either through the default harness list or an explicit --harness claude value.
• Your content-retention mode allows the level of prompt content your team expects to capture.

​

Collection path

Claude Code exports OTLP telemetry to the local Beacon collector. Beacon writes normalized endpoint events to the configured runtime JSONL log and makes them available in the local dashboard.

​

Discovery and status

Beacon detects Claude Code through the claude executable and Claude settings paths. Use beacon endpoint discover or beacon endpoint status to confirm that Claude Code is present and configured for local telemetry.

​

Install or configuration support

beacon endpoint install configures Claude telemetry settings so Claude Code sends OTLP data to the local collector. Claude Code is not currently configured through Beacon’s hook adapter.

​

Telemetry coverage

​

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, and loads the local collector LaunchDaemon. 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