{"version":"2.1.311","anchor":"sdk-tengu-sdk-stall-timer-re-arms-instead-of-resetting-on-ev","canonical_anchor":"sdk-tengu-sdk-stall-timer-re-arms-instead-of-resetting-on-ev","heading":"Cheaper stall timer for programs driving Claude Code","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/sdk-tengu-sdk-stall-timer-re-arms-instead-of-resetting-on-ev","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Cheaper stall timer for programs driving Claude Code\n\nThe timer that watches for stalled output to programs using Claude Code is now set once and checked, instead of reset on every message\n\n**What**\n\nWhen another program drives Claude Code through the SDK (a kit for using Claude Code from your own code), Claude Code watches for a stall, a long gap with no messages sent. It used to cancel and restart that timer on every message it wrote. It now sets the timer once and checks it against the time of the last message.\n\n**Why**\n\nIt does less work on every message, and stalls are detected the same way as before.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}