-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
Describe the bug
I had several sub-tasks running in fleet mode and I left my computer while they worked. Turns out they were complex enough they didn't finish before the PC went to sleep. I turned it back on and I can run /tasks to see them, but they seem to no longer be updating. There is no indication they are still actually working. I'm not sure if this is a presentation problem (they resume fine we just don't show it well) or a bug with subagents not being able to recover from sleep or other interruptions.
The little heartbeat icon no longer animates and duration doesn't increment, hence why I think it's frozen.
Affected version
1.0.5
Steps to reproduce the behavior
- Put copilot in /fleet mode with a few long-running tasks
- Partway through the task put the computer to sleep
- Wake it up and check /tasks and see that the progress seems frozen.
Expected behavior
I'd expect that going to sleep may cause connection errors but that upon waking, copilot is able to recover each sub-agent and continue their work. I also expect that the tasks UI is able to keep rendering updates, so I am able to track if work is really happening.
There were no errors showing up, so I'd expect those to show if there were any, but if not, I'd expect it to show work happening again.
Additional context
On Windows Terminal, Windows 11 Enterprise Insider Preview.