/ask and /btw answers go blank while the dialog stays open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
When I use /ask or its /btw alias, answer text appears and then disappears without me pressing Escape or otherwise dismissing the response. The answer box stays open but becomes blank.
This is different from the expected disappearance after explicitly closing the temporary answer panel.
Affected version
1.0.83-5
Steps to reproduce the behavior
- Run Copilot CLI in the VS Code integrated terminal on Windows.
- In an existing conversation, submit
/ask <a short text-only question>or/btw <a short text-only question>. - Allow the answer to render and leave the panel open without dismissing it.
- Observe that the answer text can disappear while the panel remains open.
This has happened repeatedly in this environment, but a deterministic minimal reproduction has not yet been isolated. It is not established whether a resumed conversation or a concurrently running main task is required.
Expected behavior
Once answer text is displayed, it should remain readable in the open panel until I explicitly dismiss it. Finishing the response should not erase already displayed text.
Additional context
- OS/architecture: Windows, x64.
- Terminal: VS Code integrated terminal.
- Related closed report: github/copilot-cli#3759 describes blank
/askresponses on resumed chats in version1.0.61. Linking as possibly related, not as a confirmed duplicate or regression.
Suspected cause, not confirmed: Completion handling may replace an already streamed answer with an empty value when the final answer payload is empty or missing. A component-level simulation reproduces that failure mode, but the final payload from an actual failing live query has not been captured.
Local workaround status: The symptom was observed before modifying the installation. A temporary local UI workaround was subsequently applied to retain displayed and buffered streamed text when the final answer is empty or missing, while still using a nonempty final answer when provided. Its effectiveness against the original live symptom has not yet been confirmed; it is not an upstream fix or proof of the suspected cause.
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 /ask and /btw in a Windows VS Code integrated terminal, including resumed conversations and concurrent tasks if possible. Compare the displayed and buffered streamed text with the final answer payload; done means the answer remains readable while the panel stays open, including when the final payload is empty or missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, vscode
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100