github / github/copilot-cli

Agent repeatedly acknowledges work without executing tool actions

未关闭
#4,566 2 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

area:agents area:tools
主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

描述

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.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

报告没有指出源文件、测试或实现入口点。首先在 Windows 上使用 PowerShell 和 gpt-5.3-codex 重现 Copilot CLI 1.0.80 中的行为,记录助手确认消息以及没有工具调用的情况。只有当执行以工具操作或明确的阻塞因素开始,而不是提出没有依据的进度声明时,才算完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
powershell, shell
领域
ai-infra-agents, cli
Issue 类型
缺陷
难度
5/5
预计耗时
一周以上
活跃度
活跃
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。