[BUG] Claude Code freezes when Terminal.app menu bar / toolbar is activated (macOS)
Resolved 💬 4 comments Opened Mar 11, 2026 by mhbmhb Closed Apr 9, 2026
Bug Description
Claude Code completely freezes when macOS Terminal.app's menu bar or toolbar is activated during a session. The TUI becomes unresponsive and requires force-killing the process.
Steps to Reproduce
- Run Claude Code in macOS Terminal.app
- During a session (especially while a tool is executing or output is being rendered), do one of the following:
- Click "Shell" menu → attempt to open a new tab
- Accidentally activate the toolbar
- Claude Code freezes immediately — the tool execution display remains on screen, no input is accepted
Expected Behavior
Menu bar / toolbar interactions should not affect the Claude Code TUI session.
Actual Behavior
- The terminal becomes completely unresponsive
- Ctrl+C does not work
- The only recovery is force-quitting the terminal or
kill -9 - This happens consistently, not intermittently
Environment
- Claude Code: v2.1.72
- Model: Opus 4.6 (Claude Max)
- OS: macOS (Darwin 24.5.0, Apple Silicon)
- Terminal: macOS Terminal.app (default)
- Shell: zsh
Screenshot
The screenshot below shows the frozen state after clicking the Shell menu. The previous session's tool output is stuck on screen.
Note: I have not tested whether this reproduces in iTerm2 or other terminal emulators. This may be specific to Terminal.app's interaction with ink/React-based TUI rendering.
Possibly Related
- #20547 (tool execution completes but never returns to prompt)
- #24478 (SIGKILL required)
- #25286 (100% write ratio in terminal renderer)
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗