Copilot CLI 1.0.84-8 does not accept interactive keyboard input in macOS Terminal

[marzann]

Describe the bug

Copilot CLI 1.0.84-8 launches its interactive interface in macOS Terminal, but it does not respond to keyboard input. The interface finishes loading and remains displayed, but typing commands or prompts has no effect.
Non-interactive mode works, and the earlier Copilot CLI 1.0.81-9 interactive interface works in the same terminal environment.

Affected version

1.0.84-8

Steps to reproduce the behavior

1. Open macOS Terminal.
2. Run: copilot
3. Wait for the interactive interface to finish loading.
4. Type a prompt or attempt to use a keyboard command.
5. Observe that the interface does not respond to keyboard input.

The cached 1.0.81-9 version accepts interactive input in the same terminal:
COPILOT_AUTO_UPDATE=false node "$HOME/Library/Caches/copilot/pkg/darwin-arm64/1.0.81-9/index.js"

Expected behavior

The interactive interface should accept keyboard input after loading, allowing prompts and commands to be entered normally.

Additional context

Operating system: macOS
CPU architecture: Apple Silicon / ARM64
Terminal emulator: macOS Terminal
Shell: zsh

The problem appears limited to the interactive terminal interface in version 1.0.84-8.
Authentication and model access work in non-interactive mode.
Version 1.0.81-9 works interactively in the same environment.

[JamesCaudill]

Seeing a similar issue on macOS Apple Silicon with 1.0.84-8. In my case, keyboard input is accepted and the prompt appears on screen, but no response starts. Running /diagnose then reports:

Cannot use /diagnose until at least one prompt has been sent.

Unlike the original report, slash commands still respond, so this may be a related prompt-submission problem rather than a complete keyboard-input failure. I have rolled back to 1.0.84-5.

[devm33]

Hi, apologies for the inconvenience here. This should be fixed in the latest 1.0.84-9 pre-release.