Finding / claude-code
2026-10-24-claude-code-runner-setup-gains-a-timeout-and-interrupted-remote-tool-outcomes-become-explicit
Runner setup gains a timeout and interrupted remote tool outcomes become explicit. 307 stops checkout hooks after 30 minutes by default and fails session setup; --checkout-hook-timeout-min changes it and 0 disables it. 309 tells the model which tool call a runner move interrupted and marks its outcome unknown. Separately, 302 hosted notes repair a failed scheduled routine restarting from the beginning an hour or more later and potentially duplicating external work.
Channel: tagged-release. Half: both. Date: 2026-10-22.
Operator consequence: Set a deliberate checkout budget and investigate slow setup before extending it. On remote recovery, reconcile the action’s external identity before retrying. The unknown-outcome notice improves the decision presented to the agent; it does not make remote effects exactly once.
Receipt
Finding metadata
Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0
Finding ID: 2026-10-24-claude-code-runner-setup-gains-a-timeout-and-interrupted-remote-tool-outcomes-become-explicit
Profile citations
- Claude Code / claim / runner-setup-and-unknown-outcomes
Source links
Primary links, including exact changelog lines when available.
- github release2026-10-24-claude-code-runner-setup-gains-a-timeout-and-interrupted-remote-tool-outcomes-become-explicitanthropics/claude-code / v2.1.302github release2026-10-24-claude-code-runner-setup-gains-a-timeout-and-interrupted-remote-tool-outcomes-become-explicitanthropics/claude-code / v2.1.307github release2026-10-24-claude-code-runner-setup-gains-a-timeout-and-interrupted-remote-tool-outcomes-become-explicitanthropics/claude-code / v2.1.309