GitHub issue #10549 in cline/cline, opened 2026-05-05 by paviko, records a report that the run_commands tool has a hard 30-second wall-clock timeout and returns a misleading error, Command failed: Command timed out after 30000ms, which the agent interprets as a system-level failure or process crash rather than the tool having stopped waiting, so the agent wastes time and tokens diagnosing a non-problem and may re-run commands that already completed in the background; the report was filed against Cline 0.0.10 (CLI, beta) on Debian 12.
Verbatim Excerpts from Cited Records
“The `run_commands` tool has a hard 30-second wall-clock timeout. When a command exceeds this limit, the tool returns:”
·
cline/cline (issue 10549 opening body, What happened? section)
·
2026-05-05T07:29:26Z
·GitHub Issue ↗
“**"Command failed"** implies the command did not execute or was rejected — but the process was actually launched and may still be running (if detached via `setsid`).”
·
cline/cline (issue 10549 opening body, What happened? section)
·
2026-05-05T07:29:26Z
·GitHub Issue ↗
“**There is no indication the timeout is a tool-side constraint** — the agent interprets it as a system-level failure or process crash, not as "I stopped waiting after 30s."”
·
cline/cline (issue 10549 opening body, What happened? section)
·
2026-05-05T07:29:26Z
·GitHub Issue ↗
“Agent concludes the command "failed" and starts debugging.”
·
cline/cline (issue 10549 opening body, What happened? section)
·
2026-05-05T07:29:26Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 7 comments were read. linear-code[bot] (2026-05-05) linked the report to CLINE-2104. minh2416294 (2026-08-03) reported a small fix ready for the misleading message and was scoping a PR for the honest-message wording, but no pull request appears in the surveyed thread. picksandshovelsapp (2026-09-07) shared a local bundle patch and linked the related VS Code issue #13246, still open with no linked PR as of that comment; Colin-Mac-Donald (2026-10-21) and sweetheart90 (2026-11-17) confirmed the workaround works for them. No maintainer fix merged and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #10549 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.