{"version":"2.1.242","anchor":"only-one-claude-code-window-per-machine-syncs-a-given-sessio","canonical_anchor":"only-one-claude-code-window-per-machine-syncs-a-given-sessio","heading":"Only one Claude Code window per machine syncs a given session","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/only-one-claude-code-window-per-machine-syncs-a-given-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Only one Claude Code window per machine syncs a given session\n\nIf the same session is open twice, only one window syncs files.\n\n**What**\n\nFile sync now takes a lock before writing, so if you have the same session open in two windows only the first one syncs. The second says so and stays quiet instead of both writing at once.\n\n**Details**\n\n- The lock is a file under a `writer-locks` directory keyed to the session's side repository.\n- If a window's lock is taken over or lost while it held it, sync stops in that window with an explicit message rather than continuing blind.\n- If the process stalls long enough to be caught by the interval check, the lock is re-taken and cached state is thrown away rather than assumed to still be valid.\n\n**Evidence**\n\n`Another Claude Code window on this machine is syncing this session's files; this one won't`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}