{"version":"2.1.296","anchor":"headless-sessions-log-when-a-host-supersedes-the-prompt-snap","canonical_anchor":"headless-sessions-log-when-a-host-supersedes-the-prompt-snap","heading":"Headless sessions now record when a host replaces the saved system prompt","tier":"internal","area":"Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/headless-sessions-log-when-a-host-supersedes-the-prompt-snap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Headless sessions now record when a host replaces the saved system prompt\n\nIn headless sessions, Claude Code now records when the host program's system prompt replaces its saved prompt, and whether that step failed\n\n**What**\n\nA headless session is one where Claude Code runs without its interactive screen, for example inside another program built with the SDK (the kit developers use to build on Claude Code). The system prompt is the set of base instructions Claude reads before a conversation.\n\nIn a headless session, Claude Code now records a diagnostic event when the host program's own system prompt takes the place of the copy Claude Code had saved. The event notes whether the prompt was rebuilt, and Claude Code also records it if that step fails.\n\n**Why**\n\nThis gives more diagnostic detail for programs built on the SDK that supply their own system prompt.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}