{"version":"2.1.283","anchor":"task-list-locking-uses-an-in-process-lock-in-diskless-mode","canonical_anchor":"task-list-locking-uses-an-in-process-lock-in-diskless-mode","heading":"The task list works without writing lock files when launched diskless","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/task-list-locking-uses-an-in-process-lock-in-diskless-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### The task list works without writing lock files when launched diskless\n\nIn diskless mode, the task list now guards its changes with in-memory locks instead of lock files on disk\n\n**Unclear.** How Claude Code decides it was launched diskless is not firmly established.\n\n**What**\n\nWhen Claude Code creates, resets, updates or claims items on its task list, it takes a lock first, so two changes cannot collide. These operations now take the lock through a shared step. When Claude Code was launched in diskless mode, meaning without writing to disk, that lock is kept in memory. Otherwise it still uses a lock file on disk, as before.\n\n**Why**\n\nTask tools can work on a system with no writable disk.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}