Bug: Command Code 1.56.0 TUI does not accept keyboard input on Windows

Summary

After upgrading from Command Code 1.55.0 to 1.56.0, the interactive TUI starts and renders correctly, but it no longer accepts keyboard input.

The prompt is displayed normally, but typing does not enter any text. The TUI appears to be running, but keyboard input is not being processed.

I initially suspected corrupted project/session data, but testing with a completely empty project reproduced the same issue.

This appears to be a regression in Command Code 1.56.0.

Expected Behavior

After running cmdc, the TUI should accept keyboard input in the Ask your question... prompt and respond normally to keyboard shortcuts.

Actual Behavior

The TUI renders correctly, for example:

Command Code v1.56.0

models: glm-5.3-flash with low effort · taste-1

~

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Ask your question...
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
? for shortcuts · taste on

However, keyboard input is not accepted. I cannot type a prompt into the input field.

The CLI itself starts correctly:

cmdc --version

and:

cmdc --help

work normally.

The problem is specifically with the interactive TUI and keyboard input.

I also tested an empty project, so the problem does not appear to be caused by corrupted sessions or project data.

Steps to reproduce the issue

1. Install Command Code 1.56.0:
   npm install -g command-code@1.56.0
2. Create a completely empty directory:
   mkdir test-command-code
   cd test-command-code
3. Run:
   cmdc
4. The TUI starts and displays the Ask your question... prompt.
5. Try typing any text.
6. The TUI does not accept the keyboard input.

Command Code Version

1.56.0

Operating System

Windows

Terminal/IDE

both cmd & PowerShell

Shell

No response

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

I completely reinstalled Command Code and also cleared the npm cache:

npm uninstall -g command-code
npm cache clean --force
npm install -g command-code@latest

The problem remained with 1.56.0.

I also tested my existing projects and initially suspected that the projects directory or session files might be corrupted. However, the same problem occurs with a completely empty project.

Regression test

I downgraded to Command Code 1.55.0:

npm install -g command-code@1.55.0

and disabled automatic updates using:

COMMANDCODE_SKIP_UPDATES=1

With 1.55.0, the TUI works normally and accepts keyboard input.

The same environment, terminal, and projects work correctly with 1.55.0.

Workaround

For now, I am using Command Code 1.55.0 with automatic updates disabled:

COMMANDCODE_SKIP_UPDATES=1

This completely restores normal TUI keyboard input.

Riproduci la regressione con Command Code 1.56.0 installato tramite npm in una directory vuota usando cmd e PowerShell, quindi confronta il comportamento della TUI interattiva con 1.55.0. Traccia il punto di ingresso dell’input della TUI di cmdc e aggiungi la copertura per l’input da tastiera; il lavoro è completato quando prompt e scorciatoie funzionano nei terminali Windows senza il workaround.