Harness coverage
Claude Cowork Telemetry in Beacon
Beacon validates Claude Cowork telemetry when an administrator configures OTLP export to the local collector.
May 13, 2026
What is Claude Cowork?
Claude Cowork was included in Beacon initial runtime discovery and validation support as a knowledge-worker agent surface.
Collection path: Admin-configured OTLP
Authoritative date: May 13, 2026 from v0.0.1 in the Beacon CLI changelog.
How Beacon reads Claude Cowork
Claude Cowork emits OTLP telemetry when configured by an administrator. Beacon validates the endpoint and normalizes supported prompt, command, tool, and file events.
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 where emitted through OTLP
- Command and tool telemetry where present
- File telemetry where present
- Local collector validation and runtime log output
What you can do now
- Validate that Claude Cowork points at the Beacon collector.
- Review emitted Cowork events beside other supported runtime surfaces.
- Use the runtime docs for admin configuration expectations.
Get started
- Install Beacon on the endpoint or host where telemetry is collected.
- Configure Claude Cowork OTLP export to Beacon collector.
- Run Beacon status or validation checks to confirm events arrive.