{"version":"2.1.323","anchor":"daemonjson-writes-now-locked","canonical_anchor":"daemonjson-writes-now-locked","heading":"Changes to daemon.json are refused while another Claude Code process is writing it","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/daemonjson-writes-now-locked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Changes to daemon.json are refused while another Claude Code process is writing it\n\nClaude Code now locks daemon.json while changing it, and refuses a change if another process holds the lock\n\n**What**\n\nWhen Claude Code changes its `daemon.json` file, it first creates a lock file next to it. If another Claude Code process already holds that lock, the change is refused and nothing is saved. The message says the file is being changed by another Claude Code process and tells you to delete the `.lock` file if that is not the case.\n\nBefore, the file was written without any lock.\n\n**Why**\n\nTwo Claude Code processes writing the file at the same time could overwrite each other's changes. The lock stops one update from silently wiping out another. If a process crashed and left the lock behind, deleting the `.lock` file clears it.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}