GitHub issue #13437 in cline/cline, opened 2026-08-20 by rvnlord, records a report that a Cline session fails on every run_commands call with an Invalid input error because the model omitted the documented command key and emitted the object-command shape under a guessed key, and that even when the command runs, the chat preview still shows the object placeholder instead of the command text, with Cline VS Code Extension 4.1.9 (Next), VS Code 1.132.0, PowerShell 7, and cline-pass with deepseek-v4-flash.
Verbatim Excerpts from Cited Records
“A Cline session fails on **every** `run_commands` call with: `{"error":"✖ Invalid input"}`. The model omitted the documented `command` key and emitted the object-command shape under whichever key it happened to guess that session (here `cmd`): `{ "commands": [{ "cmd": "Get-ChildItem '…'" }] }`.”
“After fixing execution, a second quirk appears: even though the command *runs*, the chat/webview **preview** of the command still shows `[object Object]` (e.g. the `run_commands` block renders `[object Object]` above the actual output).”
“The **input schema gate** used by `Mgn` to register the tool is strict: `j4o = { commands: O.array(j8t) }` — **an array of strings only**. Any object command (`{cmd:…}`, `{exec:…}`, …) fails this zod gate and the whole call returns `{"error":"✖ Invalid input"}`. The forgiving runtime layer never runs.”
“An object command item should be accepted and run regardless of which key the model guesses for the command text, while still honoring a real `args` array when present — and the chat preview should show the actual command text, never `[object Object]`.”
·
cline/cline (issue 13437 opening body, Expected behavior section)
·
2026-08-20T22:04:27Z
·GitHub Issue ↗
Counter-record: Issue is closed with 4 comments as of 2026-11-05. Maintainer saoudrizwan replied on 2026-08-21 that the issue should be fixed in v4.1.11 and asked the reporter to update and report back; no reporter confirmation appears in the surveyed thread. The issue was later marked stale by github-actions[bot] on 2026-10-21 and closed by github-actions[bot] on 2026-11-05 for inactivity, not by a maintainer as fixed. Surveyed thread contains no maintainer fix verdict beyond the v4.1.11 statement and no reporter confirmation of a fix. The claim documents only the original report, not a verified current state.
Falsification probe: If issue 13437 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.