{"version":"2.1.309","anchor":"remote-session-output-hold-no-longer-persists-once-a-model-c","canonical_anchor":"remote-session-output-hold-no-longer-persists-once-a-model-c","heading":"Remote sessions stop holding back output once Claude has started replying","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/remote-session-output-hold-no-longer-persists-once-a-model-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Remote sessions stop holding back output once Claude has started replying\n\nIn remote sessions, an empty checkpoint no longer holds back output after a model reply has started streaming\n\n**What**\n\nIn a remote session, Claude Code can hold back parts of the transcript instead of uploading them to a viewer straight away. One setting lets an empty checkpoint keep that hold in place. The hold now applies only until a reply from the model has started streaming in. After that, an empty checkpoint no longer keeps it.\n\n**Why**\n\nThis may change when held parts of the transcript are uploaded to someone watching the session.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}