{"version":"2.1.273","anchor":"metric-attribution-fields-agentskillpluginmcp-names-can","canonical_anchor":"metric-attribution-fields-agentskillpluginmcp-names-can","heading":"Metric attribution fields (agent\/skill\/plugin\/mcp names) can be redacted before emission","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/metric-attribution-fields-agentskillpluginmcp-names-can","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Metric attribution fields (agent\/skill\/plugin\/mcp names) can be redacted before emission\n\nAttribution fields like agent, skill, plugin, and MCP names can now be redacted from emitted metrics\n\n**Unclear.** The `tengu_teal_corbel_newel` gate that allows unredacted emission read off for this site's account and off for the anonymous baseline, with no reading yet taken under this release.\n\n**What**\n\nClaude Code can now redact certain attribution fields before sending out metrics: `agent.name`, `skill.name`, `plugin.name`, `mcp_server.name`, and `mcp_tool.name`. The first time one of these values would differ from a shared baseline, it gets replaced with a common placeholder value instead, unless a setting allows the real, unredacted values to be sent.\n\n**Why**\n\nThis limits how much identifying detail about which agents, skills, plugins, or MCP tools you use gets included in emitted metrics, when the corresponding setting isn't enabled.\n\n- Flag `tengu_teal_corbel_newel`: Off in both readings (read for one account on one subscription tier against v2.1.273; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}