{"version":"2.1.288","anchor":"remote-tool-serving-calls-abort-when-session-is-no-longer-s","canonical_anchor":"remote-tool-serving-calls-abort-when-session-is-no-longer-s","heading":"Remotely served tool calls now stop when the session stops being served","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-tool-serving-calls-abort-when-session-is-no-longer-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remotely served tool calls now stop when the session stops being served\n\nTool calls served to a remote session are cancelled when that session is no longer served, and broken project hooks are tracked\n\n**Unclear.** It is not clear what switches this behaviour on or what its defaults are.\n\n**What**\n\nClaude Code can run tools on behalf of a remote session. Before, only background shells stopped when that serving ended. Several other things are different now:\n\n- Tool calls still running are cancelled once the session is no longer served.\n\n- Project hooks that fell back after a timeout, an exit, a failed wrap or a malformed reply are marked as having stopped working. A hook is code that runs automatically at set moments.\n\n- Hook notices appear when you approve or decline.\n\n- If tool serving was saved as on, Claude Code waits for the flag service to answer before serving tools.\n\n**Why**\n\nThis changes how long-running remote tool calls and project hooks behave when a session ends or while a flag is still being looked up.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}