Cline keeps repeating the same tasks in Jetbrains IDE's with LM Studio #8637

Activity

1. linear commented on Jan 15, 2026

   

   linearBot

   on Jan 15, 2026 – with Linear

   More actions

   CLINE-1131
2. github-actions

   added

   JetBrainsIssues specific to JetBrains IDEsIssues specific to JetBrains IDEs

   on Jan 15, 2026
3. github-actions commented on Jan 15, 2026

   

   github-actionsBot

   on Jan 15, 2026 – with GitHub Actions

   Contributor

   More actions

   Hey @hendrikras, thanks for reporting this!

   The behavior you're describing - seeing the same API requests sent multiple times and Cline repeating responses/tasks - is a known pattern that occurs with local models, particularly when running through LM Studio. This is almost certainly model behavior rather than a Cline bug.

   What's happening

   When local models struggle with Cline's tool-calling format, they can enter repetitive loops where they either:

   1. Output the same text multiple times without properly executing tools
   2. Fail to format tool calls correctly, causing Cline to retry the request

   The fact that it works via OpenRouter with the same model suggests the issue may be related to how LM Studio handles streaming responses or tool calls differently, or possibly timeout/context configuration differences.

   Things to try

   1. Enable Compact Prompts (most impactful)
   Go to Cline Settings → Features → "Use Compact Prompt" and toggle it ON. This reduces prompt size by ~90% and helps local models follow the expected format more reliably.

   2. Check your LM Studio settings
   The LM Studio setup guide recommends:

   • Context Length: Set to the model's maximum (262,144 for Qwen3-Coder-30B)
   • KV Cache Quantization: Leave unchecked (important for consistent performance)
   • Flash Attention: Enable if available

   3. Model recommendation
   For best results with Cline + LM Studio, the docs recommend Qwen3 Coder 30B A3B Instruct. Which model are you currently using?

   4. Verify JetBrains plugin version
   You're on v1.1.20 - that should be recent. However, there was a confirmed looping regression in v1.1.5 (Cline v3.38.x) that was fixed in later versions. If you're experiencing this with all tasks consistently, it might be worth checking if your internal Cline version aligns with the plugin version.

   Clarifying questions

   Could you share:

   1. Which model are you running in LM Studio?
   2. What's your configured context length in LM Studio?
   3. Can you see any specific error messages in the LM Studio developer logs when the repetition occurs?

   This info would help maintainers determine if there's something specific to the JetBrains + LM Studio combination causing this.

   ---

   Possible Duplicates:

   • Infinite looping from Devstral-2 123b #8120 - "Infinite looping from Devstral-2 123b" (JetBrains, multiple local models reported similar behavior)
   • Why does Cline get stuck on API Requests when using a local model via LM Studio #8044 - "Why does Cline get stuck on API Requests when using a local model via LM Studio"
   • Cline enters infinite repetitive loop with Gemini 2.5 Pro, repeating same response without tool execution #5625 - "Cline enters infinite repetitive loop" (closed as model quality issue)
   • Cline repeating tool calls plus checkpoints indefinitely. #7585 - "Cline repeating tool calls plus checkpoints indefinitely" (confirmed v3.38.x regression, now fixed)
   • Phi4 Ollama Iterates Same Answer. #1220 - "Phi4 Ollama Iterates Same Answer" (similar pattern with local models)
4. github-actions

   added

   Model QualityIssues caused by model limitations, not Cline bugsIssues caused by model limitations, not Cline bugs

   Needs User InputWaiting for more information from the reporterWaiting for more information from the reporter

   Bot RespondedIssue has received an automated responseIssue has received an automated response

   on Jan 15, 2026
5. github-actions commented on Mar 17, 2026

   

   github-actionsBot

   on Mar 17, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue is stale because it has been open for 60 days with no activity.
6. github-actions

   added

   staleAuto-applied to inactive issuesAuto-applied to inactive issues

   on Mar 17, 2026
7. wchoi32

   added a commit that references this issue on Mar 23, 2026

   feat: add doom loop detection for repeated identical tool calls

   ...

   311f576
8. ClineXDiego commented on Mar 24, 2026

   

   ClineXDiego

   on Mar 24, 2026

   Contributor

   More actions

   Thanks for reporting this. PR #9933 was just merged — it adds detection for repeated identical tool calls, which should catch the repeating task loop you described. Expect the fix in the next release. Feel free to reopen if you still see it after updating.
9. ClineXDiego

   closed this as completedon Mar 24, 2026