Text cursor not present in input field

[PEERSOFTdev]

Describe the bug

A text (blinking) cursor, usually found in terminals, e.g. at the terminal prompt, does not appear in Copilot's UI, thus not signaling the next character position to type. This way Screen Readers have no indication of an insertion point.

Affected version

Version: 0.0.333, Commit: 4cbf3da

Steps to reproduce the behavior

1. Start Narrator (Ctrl+Shift+ENTER).
2. Type "copilot" at the terminal prompt (e.g. in Windows Terminal). You hear typed characters as the Narrator announces keys pressed.
3. Try to move by Left/Right cursor keys - Narrator will read what you've typed so far.
4. Press ENTER to open Github Copilot CLI.
5. As soon as you encounter its prompt, type anything - Narrator still announces characters typed, but just because the default mode is to speak typed characters (character keys, not actually entered characters).
6. Now press Left/Right cursor keys - Narrator does not speak what you were typing.

Expected behavior

Narrator should announce the character at the insertion point.

Additional context

openai/codex does the thing right.

[RyanHecht]

Thanks for the report -- we do show a cursor, but we should look into why Narrator is not announcing it correctly. Prioritizing this for the team to look at!

[PEERSOFTdev]

Hi, there is v0.0.354 and the blinking cursor isn't still visible for me. When I try with the NVDA screen reader with a Braille display that is able to blink by dot cells 7-8 at the cursor position, when launching Copilot I can observe the following behaviour:

• The last three lines of the screen are as follows:

• Enter @ to mention files or / for commands
  Ctrl+c Exit · Ctrl+r Expand recent
  ‍
  NVDA shows me the blinking cursor at the very last line, beside the ‍ (zero-width joiner) character, whereas it should show it on the line with the > symbol. As soon as I type anything, e.g. "ahoj", I see these four letters written just beside the > symbol, but the cursor stays still where i said.