Observação
GitHub Copilot usage metrics are currently in public preview with data protection and subject to change.
Lines of Code (LoC) metrics offer a directional way to measure Copilot’s tangible output. These metrics quantify how many lines Copilot suggested, added, or deleted in the editor—helping enterprise administrators understand Copilot’s contribution to the codebase over time.
LoC metrics may vary across IDEs and versions. Keep the following considerations in mind:
- Coverage: Not all IDEs and users will emit LoC telemetry until they upgrade to the required versions. Reports include the
last_known_ide_versionandlast_known_plugin_versionfields so you can monitor coverage across your enterprise. - Stability: As Copilot evolves, telemetry definitions may change. Expect small shifts in data as accuracy improves over time.
Version requirements
LoC metrics require specific minimum versions of IDEs and Copilot plugins to function. Users on older versions will not contribute LoC data, which may lead to underreporting until they upgrade.
| IDE | Feature | Minimum IDE version | Minimum Copilot Chat extension version |
|---|---|---|---|
| Eclipse |
| 4.31 | 0.9.3.202507240902 |
| 4.31 | 0.11.0.202508291001 | |
| 4.31 | 0.10.0.202508110512 | |
| IntelliJ/JetBrains |
| 2024.2.6 | 1.5.52-241 |
| Visual Studio |
| 17.14.13 | 18.0.471.29466 |
| 17.14.14 | 18.0.471.29466 | |
| VS Code |
| 1.104.0 | 0.31.0 |
| 1.102.0 | 0.29.0 | |
| 1.103.2 | 0.30.3 | |
| 1.103.0 | 0.30.0 | |
| XCode |
| 14.3.1 | 0.40.0 |
| 15.0 | 0.43.0 | |
| 15.2 | 0.41.0 |
Available LoC metrics
LoC metrics are included in:
- The Copilot user-level report
- The Copilot usage metrics API
They are not included in the Copilot usage metrics dashboard.
LoC metrics measure Copilot’s activity across completions, chat, and agent features. For detailed field descriptions and definitions, see Data available in Copilot usage metrics.
How agent mode affects LoC metrics
Unlike completions or chat, Agente do Copilot does not follow a “suggest then accept” flow. Agents plan and execute multi-step tasks, often editing multiple files iteratively without explicit acceptance by the user. Because of this, LoC metrics for agent activity are measured differently.
| Behavior | How it’s reflected in LoC metrics |
|---|---|
| Agent code suggestions | Counted as loc_suggested_to_add_sum when visible code blocks are shown in the chat panel. |
| Agent edits in files | Counted as loc_added_sum and loc_deleted_sum under the agent_edit feature bucket. These edits are not included in suggested metrics. |
| Multi-file operations | Each file edit contributes to total added and deleted lines, even if triggered by one prompt. |
Example output for agent-related LoC activity:
"totals_by_language_feature": [
{
"language": "unknown",
"feature": "chat_panel_agent_mode",
"code_generation_activity_count": 12,
"code_acceptance_activity_count": 0,
"loc_suggested_to_add_sum": 86, // code block suggestions in chat panel in agent mode
"loc_suggested_to_delete_sum": 0,
"loc_added_sum": 5, // only includes code block copy or apply in chat panel, not agent edits
"loc_deleted_sum": 0
},
{
"language": "unknown",
"feature": "agent_edit",
"code_generation_activity_count": 345,
"code_acceptance_activity_count": 0,
"loc_suggested_to_add_sum": 0,
"loc_suggested_to_delete_sum": 0,
"loc_added_sum": 2342, // agent and edit mode edits in files
"loc_deleted_sum": 947
}
]
For a single agent edit, you may see metrics such as:
"user_initiated_interaction_count": 0,
"code_generation_activity_count": 1,
"code_acceptance_activity_count": 0