{"version":"2.1.319","anchor":"gateway-routed-background-sessions-are-not-restarted-after-a","canonical_anchor":"gateway-routed-background-sessions-are-not-restarted-after-a","heading":"Background sessions on an LLM gateway are not restarted after a crash","tier":"notice","area":"Sessions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gateway-routed-background-sessions-are-not-restarted-after-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Background sessions on an LLM gateway are not restarted after a crash\n\nA crashed background session that runs through an LLM gateway is no longer restarted automatically, even when its saved state reads success\n\n**What**\n\nThe automatic restart of a background session that crashes after its saved state reads success now has one more condition. The session must not be held on an LLM gateway. An LLM gateway is a server that sits between Claude Code and the model provider and passes requests along.\n\nClaude Code reads a mark saved for each session that says whether it uses a gateway. If it cannot read that mark, it logs a message and treats the session as if it uses a gateway, so it is not restarted.\n\n**Why**\n\nBackground sessions on an LLM gateway are handled differently when Claude Code updates or recovers from a crash. If you use a gateway, expect a crashed background session to stay stopped rather than come back on its own.\n\n- Flag `tengu_bg_settled_crash_restart`: Not enough to say (read for one account on one subscription tier against v2.1.319; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}