Allow multi-turn conversations inside /ask
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 feature or problem you'd like to solve
The /ask command isolates a question from the main conversation, but it only supports one turn. When Copilot asks for clarification, the user cannot answer within the same /ask context.
Proposed solution
Keep /ask isolated from the main conversation while allowing multiple turns inside the same /ask view.
- Keep the input available after each response.
- Include previous
/askmessages when processing follow-up questions. - Preserve this local context until the user closes the
/askview. - Let
Escclose the side conversation and return to the main session. - Do not add the side conversation to the main session unless the user explicitly chooses to do so.
This preserves the purpose of /ask, which is avoiding changes to the primary conversation, while allowing users to clarify questions and reach a useful answer.
Example prompts or workflows
- Run
/ask Why does this API require a cancellation token?. Copilot asks which runtime or API version is being used. Answer inside the same/askview, then receive a response that uses both messages. - Run
/ask Compare these two implementation approaches. Copilot asks which constraint matters most. Supply the constraint without adding either message to the main session. - Run
/ask Explain this error. Copilot asks for a missing command or version. Provide it, receive the explanation, then pressEscto return to the unchanged main session.
Additional context
This replaces #4538 and #4577, which were submitted without the Feature Request form.
Related requests:
- #92 requests a broader conversation mode that does not perform agent actions.
- #2885 documents the current dead end when
/askproduces a response that requires follow-up interaction.
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 at the /ask command entry point and reproduce a clarification flow with a follow-up question. Trace how the side view handles input and context, then verify that prior /ask messages persist until Esc, remain isolated from the main session, and support multiple turns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100