{"version":"2.1.312","anchor":"auto-mode-denial-state-gains-rewrite-tracking-fields-that-re","canonical_anchor":"auto-mode-denial-state-gains-rewrite-tracking-fields-that-re","heading":"Auto mode's denial tracking now also resets rewritten-action records","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/auto-mode-denial-state-gains-rewrite-tracking-fields-that-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Auto mode's denial tracking now also resets rewritten-action records\n\nResetting auto mode's denial count now also clears three new records that follow rewritten tool actions\n\n**What**\n\nIn auto mode, Claude Code decides for itself whether an action needs your approval. It keeps a running record of denied actions, meaning actions it was not allowed to take. When that record is reset, it now clears three more pieces of state alongside the count of denials in a row and the timed-fallback notice:\n\n- `lastRewriteMessageId`\n\n- `lastRewriteFingerprint`\n\n- `rewriteDenials`\n\nBefore this release, a reset cleared only the count of consecutive denials and whether the timed-fallback notice had been shown.\n\n**Why**\n\nThe new fields suggest that auto mode now keeps a separate count of denials for actions that were rewritten. A tool action is the step Claude takes, such as running a command or editing a file. Because these fields are cleared at the same moment as the existing counters, a fresh start in auto mode clears all of this tracking together.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}