Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C067 Supported 2026-11-08

GitHub issue #13380 in cline/cline, opened 2026-08-19 by D-Alex, records a report on Cline CLI 3.0.55 that an interactive session stops producing output mid-task and never returns control to the prompt, with no error and no timeout, that hub-daemon.log shows for 4 sessions running the identical prompt a capability.request.start for hook.afterRun with no matching capability.respond, staying open until the client process is killed, and that the identical prompt hung 4 out of 4 times while a control run with the missing file added to the repo completed normally.

Verbatim Excerpts from Cited Records
“Interactive session stops producing output mid-task and never returns control to the prompt. No error, no timeout. Only recovery is SIGINT, which kills the process and drops the session.”
— D-Alex · cline/cline (issue 13380 opening body, Symptom section) · 2026-08-19T16:12:50Z ·GitHub Issue ↗
“`hub-daemon.log` shows, for 4 sessions running the identical prompt, a `capability.request.start` for `hook.afterRun` with no matching `capability.respond`. It stays open until the client process is killed, at which point:”
— D-Alex · cline/cline (issue 13380 opening body, Root cause section) · 2026-08-19T16:12:50Z ·GitHub Issue ↗
“`hook.afterRun` should get the same enforced timeout `hook.onEvent` already has (fail the run with a visible error), or be redelivered on client reconnect instead of orphaned indefinitely.”
— D-Alex · cline/cline (issue 13380 opening body, Expected section) · 2026-08-19T16:12:50Z ·GitHub Issue ↗
“Ran the identical prompt 4 times (fresh session each time): 4/4 hung, each confirmed via the `hook.afterRun` log signature above. In every case the hang lands exactly at the tool_result → next-continuation boundary — never mid-stream, never on the initial user turn.”
— D-Alex · cline/cline (issue 13380 opening body, Steps to reproduce section) · 2026-08-19T16:12:50Z ·GitHub Issue ↗
Counter-record: Closed 2026-11-07 by github-actions[bot] because the issue had been inactive for 14 days since being marked stale on 2026-10-20; the closure is an automated stale-close, not a fix confirmation, and no fix or maintainer response appears in the 3 comments read (all 3 read: the linear-code bot linkback to CLINE-3024, the stale notice, and the stale-close notice). No reproduction dispute appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If issue 13380 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.