VS Code Copilot Chat Telemetry in Beacon

What is VS Code Copilot Chat?

VS Code Copilot support gives Beacon prompt, model, session, and tool events from Copilot Chat while filtering low-value noise.

Collection path: Copilot Chat OTel plus optional preview hooks

Authoritative date: May 27, 2026 from v0.0.31 in the Beacon CLI changelog.

How Beacon reads VS Code Copilot Chat

Beacon normalizes VS Code Copilot Chat OTel spans into vscode_copilot events and optionally uses hooks for extra lifecycle and cross-agent detail when enabled by the organization.

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

• Copilot session, prompt, model, and tool activity
• Low-noise filtering for repeated spans and metrics
• Optional hook detail for lifecycle and cross-agent events
• Separate attribution from GitHub Copilot CLI

What you can do now

• Monitor Copilot Chat usage inside VS Code.
• Avoid mixing vscode_copilot and copilot_cli in dashboards.
• Use optional hooks when organizational settings enable them.

Get started

1. Configure VS Code Copilot OTel export to the Beacon collector.
2. Optionally install preview VS Code hooks.
3. Use Beacon discovery and runtime logs to verify vscode_copilot events.

Source references

• Runtime docs
• Source reference