Preserve question_tool rendered output (description/question/choices) when user presses Escape to dismiss
- Linguagem predominante
- Shell
- Estrelas
- 11.2k
- Forks
- 1.9k
- Merge médio
- 14h 16min
- PRs com merge (30d)
- 6
Descrição
### Describe the bug
When the agent presents a question or multiple-choice prompt, pressing Escape to dismiss it (e.g. to run a quick `!` shell command or interact with the agent differently) causes the entire question block to collapse into a single unreadable line. The original multi-line formatting — choices, context, spacing — is lost.
This makes it difficult to reference what the agent asked, especially when you want to come back and answer the question after checking something first.
### Steps to reproduce
1. Give the agent a prompt that triggers a question with multiple choices
2. Agent renders a nicely formatted question with options
3. Press **Esc** to dismiss the question (e.g. to run a `!` command first)
4. Observe: the question collapses into a single line of concatenated text, losing all formatting
### Expected behavior
When a question/choices prompt is dismissed via Escape, the rendered text should preserve its original multi-line formatting. The question should remain readable in the conversation history so the user can:
- Reference it after running a quick shell command
- Copy/paste from it
- Re-read the options before deciding how to respond
### Additional context
This is a common workflow — the agent asks a question, but before answering you want to check something (e.g. `!ls`, `!git status`, `!cat some-file`) to make an informed choice. The collapsed question text makes it hard to remember what was asked.
Related to #2733 Agent pushes user toward implementation choices while still in plan mode
Guia de contribuição
Direção de pesquisa
Comece reproduzindo o fluxo de question_tool com um prompt de múltipla escolha e, em seguida, acompanhe o que acontece quando Escape o descarta e a saída renderizada é adicionada ao histórico da conversa. O trabalho estará concluído quando a descrição, a pergunta, as opções, o espaçamento e as quebras de linha continuarem legíveis após o descarte; nenhum arquivo ou teste é mencionado na issue.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- shell
- Domínio
- cli
- Tipo de issue
- Bug
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 50/100