CommandCodeAI / CommandCodeAI/command-code
Repetitive/inefficient thinking
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 4k
- Forks
- 350
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es wird keine Quelldatei oder kein Test genannt. Beginne damit, das Verhalten mit Mimo v2.5Pro unter Windows in VS Code zu reproduzieren, beobachte die Verarbeitung mit Ctrl+O und zeichne auf, ob sich dasselbe Reasoning vor dem Netzwerkfehler wiederholt. Als erledigt gilt die Aufgabe, wenn der Agent redundante Verarbeitung und Token-Nutzung vermeidet, ohne die gemeldete Fehlerbehandlung zu verschlechtern.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- node.js, vscode
- Bereich
- ai, cli
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100