{"version":"2.1.238","anchor":"more-context-attached-to-permission-and-request-telemetry","canonical_anchor":"more-context-attached-to-permission-and-request-telemetry","heading":"More context attached to permission and request telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/more-context-attached-to-permission-and-request-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### More context attached to permission and request telemetry\n\nPermission and request telemetry now carries more detail, including whether hooks ran.\n\n**What**\n\nPermission and tool events now carry `hooks_applied` and a snapshot of session state, request content events count narration blocks, MCP server-instruction changes report how many instructions were added, and the held, superseded and fallback-reask permission outcomes now share one common set of extra fields.\n\n**Evidence**\n\n`hooks_applied`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}