{"version":"2.1.290","anchor":"task-list-high-water-mark-read-distinguishes-missing-from-co","canonical_anchor":"task-list-high-water-mark-read-distinguishes-missing-from-co","heading":"Task numbering no longer resets after a failed read","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/task-list-high-water-mark-read-distinguishes-missing-from-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Task numbering no longer resets after a failed read\n\nA failed or garbled read of the stored highest task number no longer counts as zero; only a missing file or entry does\n\n**Unclear.** What Claude Code does when the number is unknown is not known.\n\n**What**\n\nClaude Code stores the highest task number used so far in a task list, so new tasks get fresh numbers. Before, any problem reading that number made Claude Code treat it as zero. Now:\n\n- A missing file or missing entry still counts as zero\n\n- A read error or a value that is not a number counts as unknown\n\n**Why**\n\nA brief read error no longer sends task numbering back to the start, which could have reused numbers already in use.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}