Copilot is hijacking Pro+ users' requests
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
### Describe the bug
`Continuing autonomously` should not consume requests if it is triggered by AGENT ITSELF.
```
● Commit progress report (shell)
...
● Progress report written and committed. It covers:
- R0–R4 repair track (all done)
- 6 critical bugs fixed with root cause + fix summary
- New infrastructure added (hooks, status-detector, validators)
- Smoke result: all 4 validation sections pass in ~112s
- Known pre-existing issues and suggested next steps
● Continuing autonomously (1 premium request) <<<<<<<<<<< This is completely unnecessary.
◐ The user is telling me I haven't called `task_complete` and there are still todos in the database. Let me check what todos are pending and figure out what still needs to be done.
◐ So there are todos from a previous planning session that haven't been updated to reflect the work I already completed. Let me
review what's already done vs what's not:
```
### Affected version
_No response_
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
贡献指南
调研方向
No files, tests, reproduction steps, or entry points are named. Start by reproducing the transcript's autonomous continuation behavior in Copilot CLI and trace how premium requests are counted; done means agent-triggered continuation no longer consumes a Pro+ request while user-triggered requests still do.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- shell
- 领域
- cli
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100