{"version":"2.1.288","anchor":"transcript-hydration-takes-a-lock","canonical_anchor":"transcript-hydration-takes-a-lock","heading":"Saving conversation records from remote sessions now takes a lock","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/transcript-hydration-takes-a-lock","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Saving conversation records from remote sessions now takes a lock\n\nLoading a remote session's transcript and writing subagent transcripts now happen under a lock so only one writer works at a time\n\n**Unclear.** It is not clear how the lock behaves when the file is already locked, such as whether it waits or gives up.\n\n**What**\n\nA transcript is the saved record of a conversation. When Claude Code fills in a transcript from a remote or cloud session, and when a subagent (a helper Claude that works on a side task) writes its transcript, it now takes a lock on the file first. A lock lets only one process write to the file at a time.\n\n**Why**\n\nTwo processes writing the same transcript at once could leave it damaged. The lock stops that.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}