CLI keyboard input broken in SSH terminal sessions after 2.1.30 update (Windows OpenSSH + Termius iOS)
Status Fixed / completed
Reported on v2.1.29
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 5 comments · opened Feb 4, 2026 · closed Feb 4, 2026
Bug Description
After the Claude Code CLI auto-updated from 2.1.29 → 2.1.30, keyboard input completely stops working in the interactive TUI chat field when accessing the CLI over SSH from a mobile terminal emulator (Termius on iOS → Windows OpenSSH → PowerShell).
The keyboard simply does not register any input in the chat field. Rolling back to 2.1.29 via npm install -g @anthropic-ai/claude-code@2.1.29 immediately fixes the issue.
Environment
- CLI version (broken): 2.1.30
- CLI version (working): 2.1.29
- Host OS: Windows 11 (Build 26200.7623)
- SSH server: Windows built-in OpenSSH
- Default shell: PowerShell
- SSH client: Termius on iOS (iPhone)
- Installation method: Standalone binary at
~/.local/bin/claude(auto-updated viaautoUpdatesChannel: "latest")
Steps to Reproduce
- Have a Windows machine with OpenSSH server enabled (default shell: PowerShell)
- Install Claude Code CLI 2.1.30
- SSH into the machine from Termius on iOS
- Run
claudein the PowerShell session - Attempt to type in the interactive chat field → keyboard input is not registered
Expected Behavior
Keyboard input should work in the interactive TUI, as it did in 2.1.29.
Actual Behavior
The TUI renders correctly but the chat input field does not accept any keyboard input. No error messages are shown.
Workaround
Roll back to 2.1.29:
npm install -g @anthropic-ai/claude-code@2.1.29
Additional Context
- The issue is specific to SSH sessions — the CLI works fine when run locally or through VS Code's integrated terminal
- The binary auto-updated at ~14:43 local time; the issue appeared immediately after
- Git Bash as an intermediary shell (PowerShell →
bash -l→claude) was being explored as a workaround but the version rollback resolved it autoUpdatesChannelhas been changed to"stable"to prevent recurrence
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Likely same root cause as #22906 - SessionStart hooks are broken in 2.1.30.
If you have any plugins enabled that use SessionStart hooks (superpowers, beads, etc.), try disabling them in
~/.claude/settings.jsonand restart. This fixed keyboard input issues for others on Windows.@s070681 Thanks for the info! I had already rolled back to solve the issue and posted merely so Anthropic could know about it, but I am much grateful for you answer!
@s070681 Did as you said and indeed, the original problem was the session start hook. Closing, and once again, thanks!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.