Claude Code Telemetry in Beacon

What is Claude Code?

Claude Code was one of Beacon initial runtime integrations. It remains the reference path for local OTLP plus optional hook telemetry.

Collection path: Local OTLP export plus optional hooks

Authoritative date: May 13, 2026 from v0.0.1 in the Beacon CLI changelog.

How Beacon reads Claude Code

Beacon configures Claude Code to export OTLP telemetry to the localhost collector and can also install managed Claude hooks in user or project settings.

The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.

Telemetry coverage

• Prompt telemetry through OTLP or hooks
• Command, tool, and file telemetry with detailed tool inputs enabled
• Token usage and cost metrics with model and session attribution
• Hook lifecycle, permission, subagent, stop, and session-end events

What you can do now

• Collect Claude Code sessions into local JSONL and the local dashboard.
• Enable detailed tool logging for command, file, URL, search, and MCP context.
• Extend local coverage with optional Claude Code hooks.

Get started

1. Run beacon endpoint install with Claude Code included in the harness list.
2. Optionally run beacon endpoint hooks install --harness claude.
3. Use beacon endpoint status or the local dashboard to verify events.

Source references

• Runtime docs
• Source reference