{"version":"2.1.290","anchor":"telemetry-events-and-host-env-allowlist-entries","canonical_anchor":"telemetry-events-and-host-env-allowlist-entries","heading":"More usage events and two hosting environment variables are now recognised","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/telemetry-events-and-host-env-allowlist-entries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### More usage events and two hosting environment variables are now recognised\n\nClaude Code's lists of allowed usage events and host environment variables gain entries about MCP, skills and hosted setups\n\n**Unclear.** What reads these new entries is not known.\n\n**What**\n\nClaude Code keeps lists of the usage events it may report and the host environment variables it passes along. Both lists gain entries:\n\n- events about an MCP server's first list of tools (MCP servers are add-ons that give Claude extra tools)\n\n- events about changes to the set of deferred tools and to MCP instructions\n\n- events about proposing skills\n\n- the environment variables `CLAUDE_CODE_HOSTED_DESKTOP` and `CLAUDE_CODE_REMOTE_TOOLS_HOST_ALLOWS_UNATTENDED`\n\n**Why**\n\nThe names point to work on proposing skills and a hosted desktop setup, but nothing here shows either doing anything yet.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}