{"version":"2.1.318","anchor":"new-telemetry-field-asked-in-directory-and-new-event-names","canonical_anchor":"new-telemetry-field-asked-in-directory-and-new-event-names","heading":"Permission prompt usage data now records the folder it was asked in","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/new-telemetry-field-asked-in-directory-and-new-event-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Permission prompt usage data now records the folder it was asked in\n\nUsage data sent for permission prompts now includes the folder the prompt was asked in, and two new field names were added\n\n**What**\n\nWhen Claude Code asks for permission to do something, it records usage data about the prompt. That data now includes `asked_in_directory`, the folder the prompt was asked in, whenever it is known. Two new field names, `resume_cache_warm` and `oauth_token_org`, were also added to the list of fields Claude Code can send.\n\n**Why**\n\nThese change only the usage data Claude Code sends. What you see and how you answer prompts stays the same.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}