{"version":"2.1.314","anchor":"held-responses-retired-when-external-loading-starts-or-a-ses","canonical_anchor":"held-responses-retired-when-external-loading-starts-or-a-ses","heading":"Held-back responses are dropped when outside loading starts or a session resumes","tier":"soon","area":"Responses","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/held-responses-retired-when-external-loading-starts-or-a-ses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Held-back responses are dropped when outside loading starts or a session resumes\n\nClaude Code now discards a held-back response and closes more dialogs when outside loading begins or a session is resumed\n\n**Unclear.** What the held-response feature is, and whether it is switched on for anyone, is not known.\n\n**What**\n\nClaude Code has the beginnings of a way to hold a response back before showing it. A held response is now discarded at two moments:\n\n- When Claude Code starts loading something from outside. At this point it also closes more kinds of dialog than the three it closed before.\n\n- When a session (one conversation with Claude Code) is resumed and swapped in.\n\nThe status line, the bar of information at the bottom of the screen, can now also be told whether a response is being held.\n\n**Why**\n\nThis points to a feature that holds a response before displaying it. In practice, a held response does not carry over once outside loading starts or a different session is resumed.\n\n- Area: Responses\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}