Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C149 Supported 2026-11-17

GitHub issue #13941 in cline/cline, opened 2026-09-08 by spollard, records a report that when read_files fails (for example ENOENT), the tool result payload correctly reports success false with an error string, but every display layer in the CLI renders the call as a success: the non-interactive stream shows a green ok, and the TUI live and session replay paths show an accent-coloured asterisk and 1 lines read from a file that does not exist; the report was filed against cline 3.0.61, also reproduced on cline nightly 3.0.61-nightly.1788783728.

Verbatim Excerpts from Cited Records
“When `read_files` fails (e.g. ENOENT), the tool result payload correctly reports `success: false` with an `error` string, and the model receives that.”
— spollard · cline/cline (issue 13941 opening body, Summary section) · 2026-09-08T04:00:53Z ·GitHub Issue ↗
“No red `x`, no `Error:`, no ENOENT text anywhere on screen.”
— spollard · cline/cline (issue 13941 opening body, Summary section) · 2026-09-08T04:00:53Z ·GitHub Issue ↗
“This matters for anyone supervising an agent from the terminal: a failed read is visually indistinguishable from a successful one, and the two TUI paths actively report "1 lines" read from a file that does not exist.”
— spollard · cline/cline (issue 13941 opening body, Summary section) · 2026-09-08T04:00:53Z ·GitHub Issue ↗
“The model itself is *not* misled — it receives the raw payload and correctly says the file is missing.”
— spollard · cline/cline (issue 13941 opening body, Summary section) · 2026-09-08T04:00:53Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 4 comments were read. linear-code[bot] (2026-09-08) linked the report to CLINE-3208. The author (2026-09-08) corrected and expanded the scope: the defect is not specific to read_files, as four tools return ToolOperationResult arrays and three of them set result to an empty string on failure, so fetch_web_content and search_codebase also render as ok, and the run_commands note in the opening body was only true of its non-zero-exit path; the author opened #13951 with a fix deriving the error from the payload. github-actions[bot] (2026-11-16) marked the issue stale after 60 days without activity. 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 #13941 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.