[BUG] TUI input completely unresponsive starting in 2.1.113 (Linux kernel 3.10)
Resolved 💬 5 comments Opened Apr 19, 2026 by foobargeez Closed May 28, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
TUI renders but accepts no keyboard input (arrows, typing, Enter all ignored). --print mode works fine. Bisected to 2.1.113 — 2.1.112 works perfectly.
Bisect:
- 2.1.91 ✅ works
- 2.1.110 ✅ works
- 2.1.112 ✅ works
- 2.1.113 ❌ broken
- 2.1.114 ❌ broken
Environment:
- Claude Code installed via npm global in a Debian 12 container
- Container host: CentOS 7, kernel 3.10.0-1160.88.1.el7.x86_64
- Container attached via docker exec -it over SSH from macOS
- Node v23.11.1 in container
- TERM=xterm-256color
Symptoms:
- TUI banner/layout renders correctly
- Escape sequences leak into input box ([>0q, [<u]9;4;0; visible as literal text)
- No keystrokes reach the TUI (tested: letters, arrows, Enter)
- Session exits cleanly at 30s with "No API key available" because auth dialog input is also dead
- Shell raw-mode input works fine outside Claude Code (read -n 1, cat, less all responsive)
- claude --print "..." works perfectly
Suspected cause: Likely a Bun runtime bump or TTY input path change in 2.1.113 that uses a syscall or epoll behavior unsupported by kernel 3.10's legacy epoll. Modern kernels likely unaffected.
What Should Happen?
TUI should be responsive
Error Messages/Logs
Steps to Reproduce
Just installing 2.1.113 in the provided environment reproduces the issue i.e., TUI goes unresponsive.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.112
Claude Code Version
2.1.112
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗