[BUG] Claude Code is crashing with a stack trace
Resolved 💬 3 comments Opened Feb 6, 2026 by asrijanga Closed Feb 10, 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?
In tmux, Claude code is consistently crashing if the focus in tmux is switched to a different pane. Unsure when this is trigger exactly.
What Should Happen?
Session inside tmux has been working well, new versions introduced this bug.
Error Messages/Logs
669: `+(c.join(" > ")+`
670:
671: No matching component was found for:
- O7 (/$bunfs/root/claude:668:20555)
- RX (/$bunfs/root/claude:668:28704)
- rO (/$bunfs/root/claude:668:28858)
- M7 (/$bunfs/root/claude:668:25070)
- <anonymous> (/$bunfs/root/claude:471:8027)
- ER (/$bunfs/root/claude:3559:4179)
- W_0 (/$bunfs/root/claude:6327:12557)
- Z$T (/$bunfs/root/claude:6340:10357)
- v1 (/$bunfs/root/claude:668:20765)
- U6 (/$bunfs/root/claude:668:39157)
Steps to Reproduce
- Create a tmux session
- Start Claude Code
- Switch to another window for a certain period of time (unsure when the issue is triggered)
- Switch back to the window with Claude Code
- You will notice a long stack trace ending with the lines above
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.17
Claude Code Version
2.1.34
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗