CommandCodeAI / CommandCodeAI/command-code
Repetitive/inefficient thinking
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Is this repetitive/inefficient thinking a model issue or something else?
It's repeating the same thing, in different words, several times:
✻ Thought for 1 second
The user is asking how to add a new provider in CommandCode. This is a question about CommandCode's features and configuration, so I should use the get_command_code_knowledge tool to get accurate information.
✻ Thought for 1 second
The user is asking how to add a new provider in CommandCode. Let me search for more specific information about provider/model configuration.
✻ Thought for 1 second
The user is asking about adding a new provider in CommandCode. This is a question about CommandCode's features and configuration. Let me get the full knowledge document to find information about providers.
✻ Thought for 1 second
The user is asking how to add a new provider in CommandCode. Let me check the configuration settings to see if there's a way
to add providers/models.
✻ Thought for 1 second
The user is asking about adding a new provider in CommandCode. Looking at the information I've retrieved, I don't see a
direct "providers" topic. However, I can see from the features that there's "Model Switching" with Alt+P. Let me search for
more specific information about providers/models.
And in the end it gave an error:
Error: 500 500 Network connection lost.
Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Trace ID: c86f75943327f3817ec9950b6b4a724d
Expected Behavior
Do not repeat the same thing over and over again, spending tokens unnecessarily/inefficiently.
Actual Behavior
It repeats the same thing over and over again, spending tokens unnecessarily/inefficiently.
Steps to reproduce the issue
I think to reproduce this problem, you'd have to interact with the model(s) and observe their processing (Ctrl+O) to see if this behavior is repeated. I discovered it this time out of curiosity; I don't know if it's happened before, although I suspect it has.
Command Code Version
1.3.1
Operating System
Windows
Terminal/IDE
vscode
Shell
cmd.exe
Additional context
The model was Mimo v2.5Pro.
System: Windows x64 · vscode · cmd.exe · Node v22.17.1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the behavior with Mimo v2.5Pro on Windows in VS Code, watching processing with Ctrl+O and recording whether the same reasoning repeats before the network error. Done means the agent avoids redundant processing and token use without regressing the reported error handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, vscode
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100