github / github/copilot-cli

/ask responses should not prompt for follow-up interaction

Abierto
#2,885 0 comentarios 0 reacciones 0 asignados Ver en GitHub
area:context-memory
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

### Describe the feature or problem you'd like to solve

/ask should not prompt for replies because the user cannot interact in a multiturn way in this side session

### Proposed solution

Description:

/ask is documented as a single-turn side question that doesn't add to conversation history. However, the model's responses in /ask sessions often propose next steps, ask follow-up questions, and prompt the user to reply — even though there's no way to interact further. The
only option is pressing Esc, which discards the entire context.

Current behavior:

- User runs /ask with a question
- Model responds with an answer, then says something like "Would you like me to dig deeper into X?" or "Here are some options — which would you prefer?"
- User has no way to respond — can only press Esc and lose the context

Expected behavior:

- Model responses in /ask should be self-contained — give the full answer without expecting follow-up
- If there are natural next steps, frame them as actions the user can take back in the main session (e.g., "To explore this further, try asking in your main session: ..."). Provide something you can copy paste from this side conversation into your main or new session to take the next steps.
- Never ask questions or prompt for replies in /ask mode

Impact: Creates a confusing dead-end experience. Users feel like they're missing functionality or hitting a bug, when it's actually the model not adapting its response style to the single-turn constraint.

### Example prompts or workflows

_No response_

### Additional context

_No response_

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza en el punto de entrada /ask de la CLI y sigue cómo se envía al modelo su contexto de un solo turno; el issue no identifica ningún archivo ni prueba. Se considera terminado cuando las respuestas de /ask son autosuficientes, nunca piden una respuesta y proporcionan prompts o acciones copiables para continuar en la sesión principal.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
shell
Área
ai, cli
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Bastante claro
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.