{"version":"2.1.281","anchor":"remote-control-can-hold-back-transcript-upload-until-a-clien","canonical_anchor":"remote-control-can-hold-back-transcript-upload-until-a-clien","heading":"Remote Control can hold back transcript upload until a client opens the session (dark-launched)","tier":"soon","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-can-hold-back-transcript-upload-until-a-clien","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control can hold back transcript upload until a client opens the session (dark-launched)\n\nRemote Control has a new mode that holds back the full transcript upload until a client opens the session, controlled by remote config\n\n**What**\n\nRemote Control connects a running Claude Code session to another app or device so you can follow or drive it from there. Claude Code does this through a component called the remote bridge. The bridge normally uploads the session's transcript, meaning the running record of messages and events. It now has a new \"deferred\" mode.\n\nIn deferred mode the bridge:\n\n- sends only a subset of messages and events, and reports `transcript_mirror: \"deferred\"`\n\n- holds back the end-of-turn `result`, unless the `eager_result` config is true\n\n- leaves `post_turn_summary`, `task_summary` and `recap` out of the metadata\n\nThe held-back transcript is released when a client opens the session, when a handoff happens, or when the controlling flag turns off. On release it back-fills up to `backfill_messages` earlier messages in batches. The default is 200, and the value is kept between 50 and 500. While uploads are deferred, a log line reads \"[remote-bridge] Transcript upload deferred until a client opens this session\".\n\nThe mode is controlled by the remote config `tengu_noble_snowflake`. Its `scope` takes one of `off`, `auto_default`, `auto`, `auto_and_sdk` or `all`.\n\n**Why**\n\nThe full history is only uploaded when someone actually opens the session. When a client does connect, it may see recent history arrive in batches, capped by the back-fill limit, instead of everything already being there.\n\n- Flag `tengu_noble_snowflake`: Not enough to say (read for one account on one subscription tier against v2.1.281; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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: Remote Control\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}