CommandCodeAI / CommandCodeAI/command-code

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

未關閉
#884 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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.

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

在空目錄中使用透過 npm 安裝的 Command Code 1.56.0,分別透過 cmd 和 PowerShell 重現此回歸,然後將互動式 TUI 的行為與 1.55.0 進行比較。追蹤 cmdc TUI 輸入進入點,並為鍵盤輸入新增覆蓋;當提示和快速鍵在 Windows 終端機中無需 workaround 即可運作時,即表示完成。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
node.js
領域
cli
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
活躍
描述清晰度
基本清楚
新手友好度
58/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。