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.

​

Codex CLI

Beacon supports Codex CLI through local OTLP logs, with optional raw Codex spans for troubleshooting.

​

Prerequisites

Before enabling Codex CLI telemetry, make sure:

• Codex CLI is installed and available as the codex 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 codex harness, either through the default harness list or an explicit --harness codex value.
• Your content-retention mode is set before rollout, especially if prompt text should be excluded from metadata-only retention.

​

Collection path

Codex CLI exports local OpenTelemetry logs to Beacon’s localhost collector. Beacon uses Codex semantic logs for session, prompt, approval, and tool-result events, and suppresses high-volume Codex spans and metrics by default. Use --include-codex-spans during install or repair only when you need raw Codex spans for troubleshooting.

​

Discovery and status

Beacon detects Codex CLI through the codex executable and ~/.codex/config.toml. Use beacon endpoint discover or beacon endpoint status to confirm that Codex CLI is present and configured.

​

Install or configuration support

beacon endpoint install writes Codex OTLP exporter tables to ~/.codex/config.toml. Beacon also configures Codex so prompt text is excluded from metadata-only retention. Codex CLI 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