{"version":"2.1.321","anchor":"exit-time-config-writes-now-take-the-config-lock","canonical_anchor":"exit-time-config-writes-now-take-the-config-lock","heading":"Settings saved on exit wait for other Claude Code windows","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/exit-time-config-writes-now-take-the-config-lock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Settings saved on exit wait for other Claude Code windows\n\nGlobal and project settings saved as Claude Code exits now take a lock, and a save that would lose data is dropped if another copy holds it\n\n**Unclear.** Whether this locking only runs when a remote switch is on is not settled.\n\n**What**\n\nWhen Claude Code exits, it saves global and project settings. Those saves now try to take a lock, a marker that stops two copies of Claude Code writing the same file at once. Before, they wrote straight to the file.\n\n- If another copy holds the lock and the save would lose data, the save is dropped\n\n- If the lock is briefly busy, Claude Code tries again\n\n- If the lock is lost or taken over, Claude Code stops treating it as held\n\n**Why**\n\nIt reduces the chance of several Claude Code windows overwriting each other's changes to `~\/.claude.json` as they close.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}