{"version":"2.1.290","anchor":"mcp-tool-idle-timeout-watchdog-gains-an-extra-timer-cleanup","canonical_anchor":"mcp-tool-idle-timeout-watchdog-gains-an-extra-timer-cleanup","heading":"MCP tool idle timeout now clears an extra timer when a call ends","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-tool-idle-timeout-watchdog-gains-an-extra-timer-cleanup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP tool idle timeout now clears an extra timer when a call ends\n\nWhen an MCP tool call finishes, Claude Code's idle-timeout check now also clears a second timer; its error text is unchanged\n\n**Unclear.** What the extra timer is for is not settled.\n\n**What**\n\nWhen an MCP tool call (a request to an outside tool you connected) finishes, the check that watches for the call going idle now clears one more timer than before. The idle timeout itself and its error message, which points to `CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT`, are unchanged.\n\n**Why**\n\nThis is small housekeeping that stops a timer from being left behind after a call; nothing visible changes.\n\n- Area: MCP\n- Names: `CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}