Autopilot agent gets stuck
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
On Copilot Desktop 1.1.15 on Windows, using embedded agent runtime 1.0.83-5, an Autopilot coordinator can become stuck after its model turn finishes but the overall task never emits session.task_complete. Cross-session messages continue entering the pending queue, while repeated assistant.idle events occur without starting a new turn—a likely lost wake-up in the pendingMessagesChanged/deferred-idle queue-drain path. Restarting the session runtime and sending a direct prompt recovers it; changing the model appears to force that reinitialization.
| Field | Value |
|---|---|
| App version | 1.1.15 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 2 (Week 1) |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the stuck Autopilot session on Copilot Desktop 1.1.15 for Windows with the embedded agent runtime 1.0.83-5. Trace the pendingMessagesChanged and deferred-idle queue-drain path around repeated assistant.idle events, and verify that queued cross-session messages trigger a new turn and ultimately emit session.task_complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ai, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100