Compact completion box randomly renders replies in a tiny inner scroll area
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Short summary
The app sometimes renders a reply inside a compact completion box. That box is only about 1/5 of the vertical window, so the result has to be scrolled inside the tiny box instead of using the full conversation view.
Affected version or release
1.1.20 (github.exe ProductVersion 1.1.20)
Installation context
Windows 11 Enterprise (build 26200), GitHub Copilot desktop app, conversation view.
What happened?
Intermittently, the app shows the model result in a compact completion box: a small nested, scrollable pane that occupies roughly one fifth of the vertical screen.
Instead of reading the answer in the normal full-height transcript, I have to scroll inside that tiny box. The rest of the window stays empty. This makes long answers and structured results hard to read.
It does not happen on every reply. It appears randomly.
Steps to reproduce
- Open a conversation in the GitHub Copilot desktop app.
- Ask for a longer structured reply (lists, explanations, multi-part results).
- Sometimes the reply renders in a compact completion box instead of the normal full-height transcript.
- Observe that the box is only a small fraction of the window height and has its own scrollbar.
I do not have a reliable repro every time. The compact completion box appears intermittently.
Expected behavior
Replies should use the normal conversation layout and the available window height. If a compact completion box is used, it should not be a tiny inner scroller that is only about 1/5 of the screen.
Additional context
Redacted screenshot of the compact completion box (content scribbled out; this is only to show the cramped inner scroll area):

The inner pane has its own scrollbar. The surrounding conversation view does not expand to use the rest of the vertical space.
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
Start by reproducing the issue in the GitHub Copilot desktop app's conversation view on Windows 11, using longer structured replies as described. Done means replies consistently use the normal available-height conversation layout, without a tiny nested scroll area or unused surrounding space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100