{"version":"2.1.288","anchor":"new-telemetry-names-and-control-request-error-codes","canonical_anchor":"new-telemetry-names-and-control-request-error-codes","heading":"Usage data covers more events and control request failures carry an error code","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/new-telemetry-names-and-control-request-error-codes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Usage data covers more events and control request failures carry an error code\n\nClaude Code reports a few more usage events, and failed requests from host apps can now include an error code\n\n**Unclear.** It is not confirmed that a projects or purge-project command exists or can be used.\n\n**What**\n\nClaude Code's usage data (anonymous reports about how features are used) now includes these events:\n\n- `cli_projects`\n\n- `cli_purge_project_dry_run`\n\n- `session_transcript_write`\n\n- `subagent_tool_resolution`\n\nEvents about creating trusted cloud repositories now also record what they cover. When a control request fails, the failure can now carry an error code. A control request is an instruction a host app sends to Claude Code. The report Claude Code makes when a feature goes wrong can no longer cause an error of its own.\n\n**Why**\n\nThe new event names hint at a projects command and a trial-run mode for purging a project.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}