/ask frequently returns no result
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
Running the /ask command often fails to return any response. The command appears to execute but no output/result is produced, with no error message shonw.
Affected version
1.0.75
Steps to reproduce the behavior
- Start a Copilot CLI session
- Run /ask
- Observe: no result is returned (not always)
Expected behavior
/ask should reliably return an answer to the given question.
Additional context
No response
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 a Copilot CLI session and repeatedly run the /ask command using the reported version, 1.0.75, to reproduce the intermittent missing response. Trace the /ask command's response handling and capture cases where it completes without output or an error. Done means /ask reliably returns an answer for the question, with a regression test covering the no-result case.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100