Skip to main content

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.

​
GitHub Copilot CLI

Beacon supports GitHub Copilot CLI through MDM-managed OpenTelemetry export to the local OTLP HTTP receiver.

​
Prerequisites

Before enabling GitHub Copilot CLI telemetry, make sure:
  • GitHub Copilot CLI is installed and available as the copilot executable for the user or managed endpoint.
  • beacon endpoint install has run so the local collector, endpoint config, and runtime log path exist.
  • The Copilot CLI launch environment sets COPILOT_OTEL_ENABLED=true.
  • The Copilot CLI launch environment sets OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318 or COPILOT_OTEL_ENDPOINT=http://127.0.0.1:4318.
  • Copilot CLI is restarted after launch-environment changes so new sessions use the updated settings.

​
Collection path

GitHub Copilot CLI exports OTLP HTTP telemetry to Beacon’s local collector. Beacon normalizes Copilot spans into endpoint events for prompt submission, session activity, tool invocation, and approval-like permission activity. Copilot CLI metrics are filtered from the local runtime JSONL log by default so endpoint timelines stay focused on user and agent activity. Use --include-runtime-metrics during install or repair only when you need low-level Copilot metrics for troubleshooting.

​
Discovery and status

Beacon detects GitHub Copilot CLI through the copilot executable or ~/.copilot/config.json. Use beacon endpoint discover or beacon endpoint status to confirm that Copilot CLI is present and exporting to Beacon’s local OTLP HTTP receiver. Beacon reports Copilot CLI telemetry as configured only when COPILOT_OTEL_ENABLED is truthy and the effective OTLP endpoint points to localhost or 127.0.0.1. If COPILOT_OTEL_FILE_EXPORTER_PATH is configured, Beacon reports Copilot as misconfigured because the file exporter bypasses the local OTLP collector.

​
Install or configuration support

beacon endpoint install prepares the collector, endpoint config, and runtime log paths. Copilot CLI telemetry is configured outside Beacon through MDM, shell profile management, or another customer-owned launch policy. Do not add Copilot CLI to the --harness list. If copilot, copilot_cli, or github_copilot is passed to beacon endpoint install --harness or beacon endpoint repair --harness, Beacon reports that Copilot CLI telemetry is MDM-managed instead of writing Copilot configuration directly. Configure Copilot CLI’s launch environment to export to the local OTLP HTTP receiver: 
export COPILOT_OTEL_ENABLED="true"
export OTEL_EXPORTER_OTLP_ENDPOINT="http://127.0.0.1:4318"
If your deployment intentionally uses Beacon’s full content retention and you want GenAI message content from Copilot telemetry, also configure: 
export OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT="true"
For a one-command local validation flow, see Test GitHub Copilot CLI telemetry.

​
Telemetry coverage

AreaSupport
Prompt telemetrySupported from Copilot chat spans when exported over OTLP HTTP
Command, tool, and file telemetrySupported for session activity, tool invocation, and permission or approval-like spans emitted by Copilot CLI
Local JSONL and dashboardSupported after events reach the local collector
MDM deploymentSupported for the endpoint agent; Copilot launch-environment configuration stays under MDM or customer policy control

​
Deployment notes

Copilot CLI currently exports OTLP over HTTP, not gRPC. Point it at Beacon’s HTTP receiver, usually http://127.0.0.1:4318, or the custom --otlp-http-port used by your endpoint install. Beacon validates the effective Copilot environment but does not write Copilot shell profiles or ~/.copilot/config.json. Keep Copilot CLI outside the default Beacon harness list, and deploy its environment settings with the same MDM or shell-management mechanism you use to launch Copilot. The older asym copilot docs cover Asymptote guardrail hooks for GitHub Copilot in VS Code. This page covers Beacon endpoint telemetry for GitHub Copilot CLI.

Supported agent harnesses

Return to the runtime support overview.

Endpoint install

Configure the local collector before enabling Copilot CLI export.