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 Cowork
Beacon supports Claude Cowork through admin-configured OpenTelemetry from Anthropic’s service.Prerequisites
Before enabling Claude Cowork telemetry, make sure:- You have Claude organization admin access to configure OpenTelemetry export.
- Beacon has a durable collector endpoint that Claude Cowork can reach; production setups should use public HTTPS.
- You have run
beacon endpoint integrations claude-cowork print-configto get the exact OTLP settings for the Claude admin console. - You can validate arrival with
beacon endpoint integrations claude-cowork validateafter Cowork activity is generated. - Your content-retention expectations match what Claude Cowork emits through OTLP.
Collection path
Claude Cowork exports OTLP telemetry from Anthropic’s service to a customer-managed collector endpoint. After events reach Beacon’s collector path, Beacon writes normalized endpoint events to the runtime JSONL log and makes them available in the local dashboard.Discovery and status
Beacon treats Claude Cowork as an admin-configured source because telemetry is enabled in Claude organization settings rather than local endpoint settings. Usebeacon endpoint integrations claude-cowork status to report whether Claude Cowork is detected and whether Cowork events have been observed in the endpoint runtime log.
Install or configuration support
Claude Cowork is configured in Claude organization settings, not bybeacon endpoint install.
Use beacon endpoint integrations claude-cowork print-config to print the OTLP settings needed for the Claude admin console, then use beacon endpoint integrations claude-cowork validate to confirm events are arriving.
Claude Cowork is not hook-based.
Telemetry coverage
| Area | Support |
|---|---|
| Prompt telemetry | Supported when emitted through Claude Cowork OTLP |
| Command, tool, and file telemetry | Supported when emitted through Claude Cowork OTLP |
| Local JSONL and dashboard | Supported after events reach the collector |
| MDM deployment | Uses a durable customer-managed HTTPS collector endpoint rather than local MDM hook config |
Deployment notes
Production Cowork telemetry should use a public HTTPS collector endpoint, not a laptop or ngrok tunnel. For testing, validate whether Cowork events have reached the runtime log before expecting them in the dashboard or downstream SIEM.Related
Supported agent harnesses
Return to the runtime support overview.
Claude Cowork commands
Print config, check status, and validate Cowork telemetry.