When copilot crashes with enqueued messages, you lose them
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the bug
I had a copilot session running and it crashed. When I resume it, the queued messages are no longer there and copilot doesn't know anything about them. In theory, I can use the arrow keys to go back through history to find them, but I've been using several other sessions and their messages show now too. I don't remember what specific messages I had in the queue.
### Affected version
GitHub Copilot CLI 1.0.43
### Steps to reproduce the behavior
Start a session
Queue several messages
Something happens that causes copilot to crash
Resume the session
Copilot doesn't know about the previously queued messages
### Expected behavior
Copilot can restore the queue messages somehow.
### Additional context
Windows 11 x64
Contributor guide
Assessment
This issue has not been assessed yet.