{"version":"2.1.268","anchor":"large-expansion-of-the-internal-telemetry-event-name-catalog","canonical_anchor":"large-expansion-of-the-internal-telemetry-event-name-catalog","heading":"Large expansion of the internal telemetry event-name catalog (Rne) plus new gate-name validators","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/large-expansion-of-the-internal-telemetry-event-name-catalog","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Large expansion of the internal telemetry event-name catalog (Rne) plus new gate-name validators\n\nClaude Code's internal telemetry catalog gained hundreds of new event names plus stricter permission-rule-name validation\n\n**What**\n\nClaude Code's internal list of telemetry and event identifiers has grown substantially, now covering areas like agents, artifacts, the bridge, ccr, MCP, sandboxing, self-hosted runners, and workflows. Alongside this, new internal constants define standard event sources (`slash_command`, `cli_flag`, `startup`, `tool`, `dispatch`, `cloud_session`) and denial reasons (`org_denied`, `cache_miss`, `route_missing`), and a new pattern now requires permission rule names to start with `allow_` followed by lowercase letters, numbers, or underscores.\n\n**Why**\n\nThis is mostly internal bookkeeping that expands what Claude Code can track and validate; the permission-rule-name pattern in particular tightens what counts as a valid rule name.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}