{"version":"2.1.282","anchor":"context-rendering-when-announced-context-fails-the-fallbac","canonical_anchor":"context-rendering-when-announced-context-fails-the-fallbac","heading":"Context delivery keeps the same format within a conversation after a failure","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/context-rendering-when-announced-context-fails-the-fallbac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Context delivery keeps the same format within a conversation after a failure\n\nIf building session context fails, Claude Code now keeps the conversation's existing delivery format instead of switching\n\n**Unclear.** It is not clear what the announced and inline formats look like in practice, or whether the one remote switch is the only thing controlling this.\n\n**What**\n\nAt the start of a session Claude Code gathers context for Claude, such as your `CLAUDE.md` files, and delivers it in one of two formats: announced or inline. It now records which format a conversation uses.\n\nIf a conversation already uses the announced format and gathering the context fails, Claude Code now keeps the announced format with empty context, and tries again after compaction (when older parts of the conversation are condensed to save space). Before, it fell back to the inline format. Such failures are now logged. Conversations detected as inline skip the announced path. That detection is controlled by a remote switch that is on unless it is switched off remotely.\n\n**Why**\n\nThis keeps context delivered in one consistent format throughout a conversation, rather than changing format partway through after an error.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}