github / github/copilot-cli

Agent repeatedly acknowledges work without executing tool actions

Aperta
#4,566 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

area:agents area:tools
Lingua principale
Shell
Stelle
11.2k
Fork
1.9k
Merge medio
14h 16m
PR unite (30g)
6

Descrizione

Preflight checklist
  • I searched existing issues to avoid creating a duplicate.
  • I understand this repository is for GitHub Copilot CLI issues.
  • I can reproduce this behavior.
Version

1.0.80

Which Copilot model are you using?

gpt-5.3-codex

What operating system are you using?

Windows_NT

What version of Node.js is installed?

N/A (not required to reproduce this conversational reliability issue)

Which shell are you using?

PowerShell

What happened?

During an active session, the agent entered a loop where it repeatedly acknowledged the user request (e.g., "I’m doing it now" / "I’m actively editing") but did not execute tool calls to perform the requested work.

This persisted across multiple user follow-ups explicitly pointing out no activity. The issue presents as task-state/progress reporting drift: the assistant claims execution has started while no action is actually taken.

Impact:

  • Breaks user trust in execution status
  • Wastes time during autopilot-style workflows
  • Can leave users unsure whether the system is hung or just misreporting state
Steps to reproduce
  1. Start a Copilot CLI session in a repository.
  2. Ask for a concrete file-edit task (e.g., "improve BACKLOG.md").
  3. Observe assistant responses claiming work has started.
  4. Continue prompting when no visible tool activity occurs (e.g., "you’re not doing anything").
  5. In affected runs, assistant may continue acknowledging without issuing execution tool calls.
Expected behavior

When the assistant says it is starting execution, it should immediately perform tool actions (read/edit/write/test as needed), or explicitly surface a blocker.

Additional context

Observed in an autopilot-mode session with repeated system reminders to continue implementation and mark completion only after actual work.

This appears to be a control-flow/reliability bug rather than a repo-specific code issue.

Logs or output

Conversation behavior is the primary evidence:

  • Multiple assistant acknowledgements of imminent action
  • No corresponding tool execution during those turns
  • User repeatedly confirms no activity is visible

If useful, I can provide a redacted transcript excerpt in a follow-up comment.

Guida per i contributori

Apri la guida per i contributori

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

Il report non indica alcun file sorgente, test o punto di ingresso dell’implementazione. Inizia riproducendo il comportamento in Copilot CLI 1.0.80 su Windows con PowerShell e gpt-5.3-codex, registrando le conferme dell’assistente e l’assenza di chiamate agli strumenti. Il lavoro è completato quando l’esecuzione inizia con azioni degli strumenti o con un blocco chiaro, invece di fare affermazioni sui progressi non supportate.

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

Valutazione

Stack tecnologico
powershell, shell
Ambito
ai-infra-agents, cli
Tipo di issue
Bug
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Attiva
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.