{"version":"2.1.317","anchor":"remote-tool-container-draining-header-handling","canonical_anchor":"remote-tool-container-draining-header-handling","heading":"Remote tool sessions notice when their host is shutting down","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-tool-container-draining-header-handling","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remote tool sessions notice when their host is shutting down\n\nClaude Code now records when a remote tool host reports it is draining, and treats some related denials differently\n\n**Unclear.** What noting a draining host or the denial handling changes for a session is not clear.\n\n**What**\n\nSome tools can run in a remote container, an isolated machine somewhere else. When that container's host reports it is draining, meaning it is shutting down and taking no new work, Claude Code now notes it. A host reports this through a response header set to 1. Two kinds of denial are now handled with this in mind: results the server is no longer holding, and calls that are unavailable because they were cut short.\n\n**Why**\n\nRemote tool sessions can now take into account that their host is going away.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}