New rendering makes it hard to determine what agent was last doing when copilot crashes
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the bug
I keep seeing copilot crash across my tabs. This is annoying, but in the past, I could scroll up to see what was last going on to simplify figuring out which session to use with copilot --resume. With the new rendering, there is nothing useful in my terminal output.
### Affected version
GitHub Copilot CLI 1.0.11
### Steps to reproduce the behavior
Run copilot, do a bunch of work, copilot crashes, nothing useful in terminal output.
### Expected behavior
Ideally, I'd like to see the copilot --resume hint when copilot crashes. Could this be modified to output this to the original stdOut when the sessionId is decided or updated?
### Additional context
I appreciate that with the new rendering the constant redraw issue hasn't been occurring anymore, but getting back to my sessions is harder.
Contributor guide
Research direction
Start by tracing the Copilot CLI rendering and crash-handling entry points, focusing on when the sessionId is decided or updated and how output reaches the original stdout. Reproduce the crash after using --resume and verify that the terminal retains a useful copilot --resume hint without disrupting the new rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100