github / github/copilot-cli

Allow multi-turn conversations inside /ask

Open
#4,579 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
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.

  1. Keep the input available after each response.
  2. Include previous /ask messages when processing follow-up questions.
  3. Preserve this local context until the user closes the /ask view.
  4. Let Esc close the side conversation and return to the main session.
  5. 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
  1. Run /ask Why does this API require a cancellation token?. Copilot asks which runtime or API version is being used. Answer inside the same /ask view, then receive a response that uses both messages.
  2. Run /ask Compare these two implementation approaches. Copilot asks which constraint matters most. Supply the constraint without adding either message to the main session.
  3. Run /ask Explain this error. Copilot asks for a missing command or version. Provide it, receive the explanation, then press Esc to return to the unchanged main session.
Additional context

This replaces #4538 and #4577, which were submitted without the Feature Request form.

Related requests:

  1. #92 requests a broader conversation mode that does not perform agent actions.
  2. #2885 documents the current dead end when /ask produces a response that requires follow-up interaction.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.