Copilot is hijacking Pro+ users' requests
- 主要言語
- Shell
- スター
- 11.2k
- フォーク
- 1.9k
- 平均マージ
- 14時間 16分
- マージ済み PR(30日)
- 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