GitHub Copilot CLI Telemetry in Beacon | Asymptote
What is GitHub Copilot CLI?
Copilot CLI support is intentionally customer-managed at launch-environment level. Beacon validates the OTLP endpoint and normalizes the telemetry it receives.
Collection path: MDM-managed OTLP HTTP
Authoritative date: May 24, 2026 from v0.0.24 in the Beacon CLI changelog.
How Beacon reads GitHub Copilot CLI
Teams configure COPILOT_OTEL_ENABLED=true and OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318 through MDM or policy. Beacon validates the endpoint and filters noisy operational metrics by default.
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 activity
- Session activity
- Tool spans
- Approval-like activity where emitted by Copilot CLI
What you can do now
- Manage Copilot telemetry through existing MDM or shell policy.
- Validate Copilot CLI status with Beacon discovery and status commands.
- Keep Copilot activity distinct from VS Code Copilot Chat.
Get started
- Set COPILOT_OTEL_ENABLED=true in the Copilot CLI launch environment.
- Set OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318.
- Run beacon endpoint status to confirm telemetry state.