github / github/copilot-cli

`ask_user` User input formatting issues

Open
#3,722 0 comments 1 reaction 0 assignees View on GitHub
area:input-keyboard area:terminal-rendering
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

### Describe the bug

When the user enters text into the "Other" section of a user response, if they go more than two lines, it just disappears (the text is recorded, you just can't see it being typed anymore). This feels really weird. I can't scroll down to see it or anything. I have to hope I spell good enough...
Something similar happens when doing a multi-line "free response" as well.

### Affected version

1.0.60

### Steps to reproduce the behavior

1. Have the agent ask you for input with a multiple choice question with "other" option and/or multi-line free response
2. Type a lot of text that takes up more than 2 or 3 lines (can make terminal smaller to force line wrap sooner).
3. See that text disappears into the darkness, also bottom divider line disappears too.

### Expected behavior

I would expect that the text area just expands to show my text similar to the normal text entry during chat. I want to always be able to see the text as I write it!

### Additional context

In both of these images I have text that continues on below the last line, it just isn't rendered.

### Other Input
Image
Note that the cursor is stuck at the end of the first line (doesn't show in screenshot)

### Multiline Input
Image
Note that the cursor is moving along the hidden bottom line but all the text is invisible (doesn't show in screenshot).

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the CLI using an ask_user multiple-choice "Other" response and a multiline free response, resizing the terminal if needed. Start by tracing the input-rendering entry point for these prompts; done means all wrapped lines and the cursor remain visible while typing, including the bottom divider.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.