{"version":"2.1.319","anchor":"stopped-by-permission-check-recorded-on-turn-outcome","canonical_anchor":"stopped-by-permission-check-recorded-on-turn-outcome","heading":"Turn records note when a permission check stopped the turn","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/stopped-by-permission-check-recorded-on-turn-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Turn records note when a permission check stopped the turn\n\nClaude Code now records when a turn was stopped by a permission check, and adds a few new internal cases for limits and MCP blocks\n\n**What**\n\nA turn is one round of you asking and Claude answering. Several small internal changes:\n\n- The record of how a turn ended now notes when it was stopped by a permission check.\n\n- Usage reports gain new entries for actions refused instead of asked about, and for a resume held back for a plan.\n\n- When Claude Code rechecks a usage limit, it now has a case for failing to look up your credits.\n\n- When an MCP server connector is blocked, repeat notices for the same server are now merged into one. MCP servers are add-ons that give Claude extra tools.\n\n**Why**\n\nThese are mostly internal signs of new handling for permissions and MCP servers. The merged MCP notices mean the same blocked server is reported once.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}