{"version":"2.1.300","anchor":"live-only-control-response-events-and-oversized-trimming-for","canonical_anchor":"live-only-control-response-events-and-oversized-trimming-for","heading":"Oversized live-only control replies kept out of uploaded sessions","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/live-only-control-response-events-and-oversized-trimming-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Oversized live-only control replies kept out of uploaded sessions\n\nWhen a session's events are uploaded, control replies marked live-only are treated as temporary and oversized ones are replaced by an error\n\n**What**\n\nWhen Claude Code uploads a session's events to the cloud, it now recognises control replies (behind-the-scenes answers between Claude Code and the service) that carry a `live_only` marker. These are treated as temporary rather than kept. If one is too large, it is replaced with an error reply.\n\n**Why**\n\nThis keeps large control messages out of saved session transcripts.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}