CommandCodeAI / CommandCodeAI/command-code

Repetitive/inefficient thinking

Aperta
#582 5 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Lingua principale
Nessun dato sulla lingua
Stelle
4k
Fork
350
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Non è indicato alcun file sorgente né alcun test. Inizia riproducendo il comportamento con Mimo v2.5Pro su Windows in VS Code, osserva l’elaborazione con Ctrl+O e registra se lo stesso ragionamento si ripete prima dell’errore di rete. Il lavoro è completato quando l’agente evita l’elaborazione ridondante e l’uso di token senza regressioni nella gestione dell’errore segnalato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
node.js, vscode
Ambito
ai, cli
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Da chiarire
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.