CLAIM C157 Supported 2026-11-18 GitHub issue #14367 in cline/cline, opened 2026-09-21 by AbubakarMahmood, records a report that restoring a workspace checkpoint can permanently delete local untracked files protected by an uncommitted .gitignore rule: git reset --hard first reverts .gitignore to the checkpoint state, then git clean -fd deletes files that are newly unignored, with no Recycle Bin or Trash fallback, and the deleted files were never captured in the stash so they are never restored; the report was filed against Cline Desktop v0.0.32 (Core SDK 3.33.x) on Windows 11.
CLAIM C160 Supported 2026-11-18 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.
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.
CLAIM C144 Supported 2026-11-16 GitHub issue #15724 in cline/cline, opened 2026-11-14 by maronsson, records a report that when selecting openrouter/auto or openrouter/auto-code under the OpenRouter provider, Cline reads output_modalities: ["text", "image"] from OpenRouter's model catalog and injects modalities: ["image", "text"] into chat completion requests, and if the user's OpenRouter workspace restricts Auto Router to text-only models, OpenRouter rejects the request with "No endpoints found that support the requested output modalities: image, text."; the report was filed against Cline 4.1.26 with qwen/qwen3.7-flash and reflection/beam-1.0-501b-a23b.
CLAIM C145 Supported 2026-11-16 GitHub issue #12977 in cline/cline, opened 2026-08-05 by boghyon, records a report that when the model calls an MCP tool via use_mcp_tool with a tool name that the connected server did not advertise, Cline forwards the call to the server unchanged, and the server then rejects it with a bare error such as "Unknown tool: 'get_note'", which is surfaced with no indication of what the valid tool names are, even though Cline already fetched and cached the server's tool catalog at connect time; the report was filed against Cline 4.1.4 (Legacy) with Anthropic Claude Opus 4.8 on a LiteLLM endpoint.
CLAIM C129 Supported 2026-11-15 GitHub issue #15360 in cline/cline, opened 2026-10-26 by gregtakacs, records a report that in long tasks the VS Code (Remote-WSL) extension host dies from V8 heap exhaustion, that Cline's panel resets and reopening the same task brings the crash back within 1-2 minutes so the task becomes a crash loop, that there were 33 of these exits in 6 days (18 on 10-21, 6 on 10-23, 9 on 10-26), and that while a turn streams the entire state is re-serialized and pushed to the webview about every 0.4-0.6 s, with one run on 10-26 issuing 1,194 of these pushes in 41 minutes, about 20 GB of JSON serialized, before the host died; the task involved had 5,824 messages and its messages file was 17.3 MB, the same size as each push. The author notes he has not proven whether the serialized strings are retained or are churn the garbage collector cannot keep up with. System cited: Cline 4.1.25, VS Code 1.142.0, Remote-WSL, Windows + WSL2.
CLAIM C130 Supported 2026-11-15 GitHub issue #15483 in cline/cline, opened 2026-11-01 by Lohnegrim, records a report of two related problems with run_commands, both measured on disk rather than inferred from chat text: (A) a tool call whose input carries an unexpected envelope is rejected with a bare Invalid input that never names the field, while the same validator does name fields for a different error class; (B) context compaction removes the examples that keep the call form correct and locks in the broken form — before the first compaction the session had made 378 run_commands calls, all of them in the correct form, and had never produced the envelope at all, while the compacted prefix retained 10 tool-call examples including 5 run_commands, all five in the broken envelope form, each followed by its retained is_error true result, and zero correct run_commands examples; after the first burst the session produced 17 consecutive rejections and never recovered on its own. System cited: Cline 4.1.26, VS Code 1.144.0, Windows 10.0.26300, provider openai-compatible via vLLM.
CLAIM C131 Supported 2026-11-15 GitHub issue #10894 in cline/cline, opened 2026-05-19 by DavidHinton-xcpc, records a report that when using VS Code Portable Mode, the MCP server configuration written into settings.json via cline.mcpServers is completely ignored by Cline, that Cline does not read MCP settings from settings.json at all and only reads from a standalone cline_mcp_settings.json file, and that MCP servers defined in settings.json do not appear in Cline's Connected MCP Servers list; the author also reports that in portable mode VS Code stores settings under the portable data directory rather than the standard path, and that the cline_mcp_settings.json file was auto-created at some point. System cited: VS Code 1.120.0 Portable Mode, Cline 3.83.0, Windows 10.
CLAIM C132 Supported 2026-11-15 GitHub issue #14013 in cline/cline, opened 2026-09-09 by reneehuang1, records a report that an ordinary message fails before streaming starts because an MCP tool's JSON Schema contains regex lookaround unsupported by the selected model provider, and the user does not need to invoke the offending tool because its schema being included in the request is enough to block the entire conversation; the concrete case is resend-mcp 2.19.1, using Zod 4.4.3, whose z.email() fields export pattern values containing negative lookaheads, which are valid JavaScript regex constructs but incompatible with the providers handling the request; Cline displays a misleading model-connection error suggesting a sign-in fix that cannot address the schema rejection; a local tools/list check returned 103 tools, with 18 lookaround-containing patterns across 14 tools; the report notes the failure was not tested with Claude Sonnet 4.5 and lists related issue #11162.
CLAIM C133 Supported 2026-11-15 GitHub issue #14026 in cline/cline, opened 2026-09-10 by damiandixon, records a report that when running the Cline plugin in CLion, and via the CLI, the server rapidly loops and spams providers.read debug logs, with hundreds of identical providers.read lines generated within milliseconds during startup and during background checks, and startup also triggers bursts of model-catalog Unknown provider id warnings for custom providers; the reporter uses a local-network LLM on an Asus GX10 running vllm, says the setup was working up to about a month ago, and expects the provider configuration read to be cached or debounced. Cline version 4.1.17, JetBrains plugin, CLion 2026.2.2, Ubuntu 22.04.
CLAIM C120 Supported 2026-11-14 GitHub issue #15690 in cline/cline, opened 2026-11-12 by Jingyi-A-Chen, records a report that in Cline CLI 3.0.74 (also seen on 3.0.73), if the model calls spawn_agent with a task that is not a string, the whole CLI process exits with code 1 with TypeError: input?.trim is not a function; the report traces the cause to spawn_agent declaring task as z.string() without validating the input before execute runs, the session callback starting handleSubAgentStart through an unawaited void invokeBackendOptional call so its rejection escapes the try/catch, and deriveTitleFromPrompt calling input.trim() on the object, with the unhandled rejection handler then ending the process; the expected behavior stated in the report is that a wrong-typed argument is answered with a tool error and the session continues.
CLAIM C124 Supported 2026-11-14 GitHub issue #9651 in cline/cline, opened 2026-03-03 by NC17z, records a report that Cline v3.69.0 consistently constructs API requests that exceed the model's maximum context window even when the user message is extremely small, across MiniMax M2.5 and Qwen models on OpenRouter, because it serializes a roughly 4,555-token tool schema into every request, adds roughly 3,000-14,000 tokens of system prompt and text input, and requests the model's full context window as max_output_tokens, exceeding the maximum context by a small margin; the report says the behavior persists even after a full wipe and reinstall of VS Code and Cline, and gives a minimal reproduction of opening a brand-new empty folder and sending a simple message such as hi.
CLAIM C125 Supported 2026-11-14 GitHub issue #15645 in cline/cline, opened 2026-11-10 by HansChundekad, records a report that in the interactive CLI with auto-approve all on (the default), a plugin beforeTool result of policy autoApprove false is ignored and the tool runs without a prompt, so a plugin cannot require user approval for a risky tool call while auto-approve all is on; with auto-approve all off, the same plugin does get a prompt, even for tools that are normally auto-approved; the report points to requestToolApproval in apps/cli/src/runtime/interactive/approvals.ts, where the auto-approve-all check returns before the request policy is read, and suggests skipping the shortcut when the policy is explicitly false, showing the prompt or denying when headless. Versions cited: Cline CLI 3.0.74 with @cline/core 0.2.0 on macOS arm64.
CLAIM C127 Supported 2026-11-14 GitHub issue #12293 in cline/cline, opened 2026-07-15 by pgalbraith, records a report that Cline 4.0.6 in the JetBrains plugin, using deepseek-chat, entered a loop repeatedly running the same directory listing commands, dir and Get-ChildItem, over 30 times without progress when asked why a CLI executable produced no output; every command returned exit code 0 with no visible output, and Cline could not capture stdout or stderr from any executed process, even simple commands whose output redirection produced no files; Cline kept retrying instead of recognizing the tool limitation, and the user had to repeatedly intervene before Cline gave up with a static analysis answer. System cited: CLion 2026.1.4, Node.js v22.15.0, x64.
CLAIM C111 Supported 2026-11-13 GitHub issue #14069 in cline/cline, opened 2026-09-11 by JimRomaineHRI, records a report that in the Cline JetBrains plugin 2.0.4, on a light IntelliJ theme, the plan-mode message banner header text and the copy icon render yellow text on a yellow background and are effectively invisible on light themes; that the report attributes this to the `--warning` custom property being static and not included in the per-theme variables IntelliJ injects onto the body, unlike `--background`, `--foreground` and `--input-*`, causing `text-warning/70` on `bg-warning/10` to fail contrast on light IntelliJ themes; that the VS Code extension does not appear to exhibit this issue; and that the static `--warning` fallback value works on dark themes but fails on light ones. No root cause beyond the reporter's stated attribution is asserted.
CLAIM C117 Supported 2026-11-13 GitHub issue #15663 in cline/cline, opened 2026-11-11 by carlosabella, records a report that in Cline 4.1.26 (VSCode Extension, macOS Sequoia 15.7.4), the skills tool description sent to the model lists only skill names, while the description from each SKILL.md frontmatter is parsed but never shown to the model until after it has already invoked the skill; as a result the model can only pick a skill by guessing from its name, and anything with a less obvious name is effectively only reachable by typing the skill name manually; the report locates the behavior in createSkillsTool in sdk/packages/core/src/extensions/tools/definitions.ts, which maps configuredSkills to names only although SkillsExecutorSkillMetadata already carries description, and says the reporter has a small fix ready plus an updated unit test.
CLAIM C105 Supported 2026-11-12 GitHub issue #14045 in cline/cline, opened 2026-09-10 by lamian521, records a report that in Cline CLI 3.0.61-nightly, fresh session/new sessions work normally, but after restoring a session with two completed turns in a new process, session/load succeeds and replays the history, yet the immediately following session/prompt emits only session_info_update and resolves with end_turn, zero new agent_message_chunk events and zero body characters, so the requested token is not recalled; the report rules out the post-load model pin as the cause, since both variants failed identically.
CLAIM C106 Supported 2026-11-12 GitHub issue #15641 in cline/cline, opened 2026-11-10 by Frederic-Demaison, records a design report that when using Cline against a local llama.cpp inference server with prompt/KV caching enabled, every Plan-to-Act toggle forces a large partial or full prompt re-prefill, measured at 17-36 s and 24k-46k tokens, even though the conversation history is unchanged, because the system prompt embeds a mode-conditional instruction block and the tool set differs between modes, with the editor hidden in Plan mode; the report proposes making the serialized prefix byte-stable across mode switches and supplies a working patch for v4.1.26 with before/after measurements.
CLAIM C086 Supported 2026-11-10 GitHub issue #15427 in cline/cline, opened 2026-10-29 by peperonid, records a report that the standalone cline-core service (JetBrains plugin) crashes repeatedly with a JavaScript heap out of memory error (exit code 134) after roughly 6-7 minutes of uptime, that heap snapshots show hundreds of retained duplicate copies of the fully serialized globalState JSON, that the on-disk globalState.json is only 2.5 KB so the 11.6 MB in-memory serialization is itself abnormally large, and that the same crash pattern repeated 3 times in 25 minutes; a later investigation note in the issue states the same root cause as issue #15031, the JetBrains host-bridge state stream queuing every snapshot without backpressure and never dropping a superseded one.
CLAIM C089 Supported 2026-11-10 GitHub issue #15031 in cline/cline, opened 2026-10-12 by mibangjie38-bit, records a report that cline-core running inside Android Studio grows until it hits the 8 GB heap limit and dies, killing the session mid-task, that the heap is 98 percent strings and it is one payload copied 1111 times, that a single suspended generator frame holds all 1111 payloads, and that the message translator cannot map session_snapshot to anything and logs and drops it while the producer keeps buffering.
CLAIM C092 Supported 2026-11-10 GitHub issue #14059 in cline/cline, opened 2026-09-11 by Energytechglobal, records a report that when multiple Cline terminals run in the same workspace, a shared relay state file can associate requests with the wrong task, that the OpenAI-compatible request does not receive a request-scoped x-litellm-trace-id header from Cline, and that when a shared relay or state workaround is used, the most recently captured task ID can overwrite the other terminal's ID, causing requests to be attributed to the wrong session; the issue proposes adding the header from the current request-scoped session ID.
CLAIM C093 Supported 2026-11-10 GitHub issue #13346 in cline/cline, opened 2026-08-18 by rvnlord, records a report that run_commands (Background Console) output reaches the LLM verbatim, ANSI escape codes included, that run_commands spawns the command with piped stdio and forwards stdout and stderr unprocessed into the tool result, and that Cline bundles strip-ansi-compatible code only inside table-layout dependencies and never applies it to command output; current behaviour is that output contains literal ANSI sequences.
CLAIM C072 Supported 2026-11-09 GitHub issue #14853 in cline/cline, opened 2026-10-06 by dominiccooney, records a report that an audit of the docs against the shipped products recorded 201 findings, that the issue tracks fixing them in 18 PRs, one per product area, and that of the 201 findings, 138 are ready to write, 59 need a quick look in the product while the PR is written, and 4 need no edit.
CLAIM C073 Supported 2026-11-09 GitHub issue #14759 in cline/cline, opened 2026-10-02 by dominiccooney, records a report that twenty images and videos in the docs show UI that has since changed, that thirteen no longer match the product while the other seven have outdated labels around content that is still right, and that each item in the issue says what is wrong and where the new file goes, so anyone with the right setup can take one. The issue remains open.
CLAIM C074 Supported 2026-11-09 GitHub issue #11370 in cline/cline, opened 2026-06-08 by galaticpower, records a report that the Cline v0.0.43 hub daemon generates a random 32-char hex auth token on startup regardless of whether the client has any auth configured, that when no CLINE_HUB_AUTH_TOKEN env var is set the client connects with no auth so the server random token does not match and the connection is rejected with code 1006, and that in the default no-auth configuration the hub should accept connections where both server and client have an empty token. The issue was closed 2026-11-08 by linear-code[bot]; no fix confirmation appears in the thread.
CLAIM C075 Supported 2026-11-09 GitHub issue #11369 in cline/cline, opened 2026-06-08 by galaticpower, records a report that Cline v0.0.43 introduced a regression in the hub daemon where WebSocket connections are rejected when the authToken is an empty string, that the XB auth-token comparison function rejects connections when the sec-websocket-protocol header contains an empty string for the auth token prefix, and that WebSocket connections should be accepted when no auth token is configured. The issue was closed 2026-11-08 by linear-code[bot]; no fix confirmation appears in the thread.
CLAIM C078 Supported 2026-11-09 GitHub issue #15579 in cline/cline, opened 2026-11-06 by The-time-forever, records a report that a saved Cline CLI 3.0.74 session cannot be resumed from /history because the Hub connection closes with code 1006 and reason Connection ended, that the Hub log records repeated abnormal socket closures with reason Received too big message, and that a session file of about 23.4 MiB containing 775 messages is a likely match for the affected session. The author states the socket-closure log entries carry no session ID, so the association cannot be confirmed from the logs alone.
CLAIM C081 Supported 2026-11-09 GitHub issue #15594 in cline/cline, opened 2026-11-08 by rjvkn, records a report that the Cline CLI splits a single assistant message into separate transcript rows when the provider interleaves reasoning chunks with text chunks, so a Thinking row is injected between the two halves of one sentence and the answer reads as if it was cut off, while the model output itself is intact. The report traces the split to use-agent-events.ts starting a new transcript entry every time the stream switches type, and notes the VS Code task path already handles interleaved reasoning while the CLI handler has no equivalent gate.
CLAIM C058 Supported 2026-11-08 GitHub issue #13365 in cline/cline, opened 2026-08-19 by gaogage, records a report that clicking Generate Commit Message in the SCM panel fails with [Commit Generation Failed] stdout maxBuffer length exceeded whenever the diff output exceeds the Node default exec buffer of 1MB, that the diff calls in apps/vscode/src/utils/git.ts go through the promisified exec and execFile wrappers without a maxBuffer option, verified on current main and in the shipped v4.1.10 bundle, and that the later truncation to 500 lines and 5000 chars happens only after exec has already killed the child process, so collecting the full stdout just to discard most of it is what breaks the feature.
CLAIM C060 Supported 2026-11-08 GitHub issue #15417 in cline/cline, opened 2026-10-28 by JoaoMarcos44, records a report verified against main commit 51f63e4fd63aeeb74d708b9c3d1f8b800aff9b3e on Windows, Node 22.16.0 and Vitest 4.0.18, that two editor calls replacing different regions of one file can both report success while one change disappears from disk, with a deterministic regression in which both calls return Edited but the final file can contain alpha new while beta stays old, and that replaceInFile and insertInFile in sdk/packages/core/src/extensions/tools/executors/editor.ts perform separate asynchronous read and full-file write operations with no coordination between editor executor instances.
CLAIM C061 Supported 2026-11-08 GitHub issue #15574 in cline/cline, opened 2026-11-06 by mwielgosz-esky, records a report on the VSCode Extension version 4.1.26, with behaviour identical on current main, that per-server autoApprove lists for MCP tools are accepted by the settings schema and read by the hub layer, but no code path consumes them when an MCP tool call is approved or prompted, so there is no configuration that makes a listed MCP tool run without prompting while another MCP tool prompts; the verified chain includes McpHub.ts reading each server autoApprove array and stamping a per-tool flag, a complete per-tool toggle disabled behind SHOW_MCP_PER_TOOL_AUTO_APPROVE set to false, buildToolPolicies forcing every discovered MCP tool to autoApprove false, and isToolAutoApproved resolving every MCP tool through the global useMcp setting.
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.
CLAIM C068 Supported 2026-11-08 GitHub issue #15561 in cline/cline, opened 2026-11-05 by Lucifergene, records a report comparing Desktop App 0.0.49 with bundled cline-cli 3.0.74 against VSCode Extension 4.1.26, that when the Anthropic provider is pointed at a custom base URL, the Desktop App and CLI request the base URL plus /messages while the VSCode Extension requests the base URL plus /v1/messages, that both surfaces read from the same ~/.cline/data directory so one stored value cannot satisfy both, and that a local HTTP stub repro observed POST /messages where /v1/messages was expected, confirmed against a real Anthropic-compatible gateway where POST to /v1/messages returned 200 and POST to /messages returned a gateway error page.
CLAIM C069 Supported 2026-11-08 GitHub issue #13384 in cline/cline, opened 2026-08-19 by rvnlord, records a report on VS Code 1.132.0 with Cline extension saoudrizwan.claude-dev-4.1.9 (Next) on Windows 10/11, that search_codebase returns files from directories the user has already excluded in their ignore files such as generated build output, that in the ripgrep fast path the custom ignore files .clineignore and .agentignore are never read by ripgrep at all and .gitignore is only honored in git-based contexts, and that in the JS fallback walker there is no ignore-file parsing anywhere in the tool path.
CLAIM C048 Supported 2026-11-07 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.