{"version":"2.1.288","anchor":"carried-writes-turn-handoff-gated-on-tengu-fizzy-petal","canonical_anchor":"carried-writes-turn-handoff-gated-on-tengu-fizzy-petal","heading":"Turn handoffs to cloud workers can now carry over pending file writes","tier":"soon","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/carried-writes-turn-handoff-gated-on-tengu-fizzy-petal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Turn handoffs to cloud workers can now carry over pending file writes\n\nA turn handoff can now carry answered Write calls to a cloud worker, which writes those files into the home folder before the turn continues\n\n**Unclear.** It is not clear how the new worker learns about and receives the carried writes from end to end.\n\n**What**\n\nA turn handoff passes an unfinished turn to a managed cloud worker, which is a remote machine that carries on the work. Handoffs could already bring attached files. They can now also carry the session's answered Write calls, where a Write call is Claude's request to create or overwrite a file. The worker writes those files into the home folder (`\/home\/claude`) at the start of the turn.\n\n- `carried_writes` is a new handoff capability. It sits in the same group as `home_files` and `file_names`, and is registered as `ccr_turn_handoff_carried_writes`.\n\n- `placeCarriedWrites` is a new handoff option next to `placeFilesByName`. It is used only when the handoff is accepted and its gate allows it. The gate is `tengu_fizzy_petal`, and nothing has been read about it yet.\n\n- Carried writes are only placed after a series of checks: the permission mode, the path rules, any hooks that would fire, the Write tool being the built-in one, limits on file count and size, the working folder being the home folder, and the Write tool's own permission result. Each failed check records a reason, and a switched-off feature records `switched_off`.\n\n- At turn start the worker waits for the feature setting to arrive before deciding.\n\n- A worker that cannot place the files refuses with `invalid_handoff: carried_writes_`. The failure reason `carried_writes_unplaceable` will not be retried.\n\n- The home-file reasons `unchecked_announcement` and `resent_announcement` and a new `ccr_upload_stream` name were also added.\n\n**Why**\n\nFiles that Claude wrote just before a handoff can now reach the cloud worker instead of being lost. Because every write still has to pass the permission and path checks, a carried write is refused rather than placed when it would not have been allowed in the first place. The feature is new code behind a gate that has not been read.\n\n- Flag `tengu_reactive_quilt`: Not enough to say (read for one account on one subscription tier against v2.1.288; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}