Input lost with iTerm & tmux integrations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 3.1k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 714
Description
What happened?
Open qwen code in a tmux window on mac/iTerm2:
$ssh my-server
my-server$ tmux -2CC
[iTerm Tmux Window]$qwen --yolo
detach session
logout
$ssh my-server
my-server$ tmux -2CC attach
[iTerm Tmux Window] attempting to type command. Qwen code will not respond to the input. However, Ctrl-Y, Ctrl-C, etc. works.
What did you expect to happen?
Command input or prompting should work after resuming tmux session.
Client information
- CLI Version: 0.0.10
- Git Commit: 5af25b26
- Session ID: cc2489b2-b215-40df-91b3-17ddd7466b86
- Operating System: linux v24.7.0
- Sandbox Environment: no sandbox
- Model Version: qwen3-coder-plus
- Memory Usage: 239.8 MB
Login information
No response
Anything else we need to know?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. First reproduce the SSH, tmux -2CC detach, logout, and reattach sequence on macOS/iTerm2, then trace the CLI's terminal input handling around session resume. Done means ordinary command input and prompts respond after reattaching, while control keys continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100