[BUG] Claude Code corrupts terminal state — new shells hang, affects other apps (macOS)

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?

Description

After running Claude Code CLI sessions, all new terminal windows hang on launch — the
shell never reaches a prompt. The Terminal.app title bar shows bash · -zsh (unusual) and
the cursor sits indefinitely with no output beyond "Last login." This also appears to be
affecting other applications — Claude.ai desktop app will not open.

The only fix is a full machine restart. The issue started today (2026-04-12) and is
reproducible — it happens again after running Claude Code.

Environment

• OS: macOS (Darwin 25.3.0)
• Shell: zsh
• Terminal: Terminal.app
• Claude Code version: Current (as of 2026-04-12)
• Model: claude-opus-4-6 (1M context)

Steps to reproduce

1. Run a Claude Code CLI session with multiple tool calls (bash commands, file

reads/writes)

1. Open a new Terminal.app window while or after the session is running
2. New terminal hangs — prompt never appears

Expected behavior

New terminal windows should open normally with a working zsh prompt, regardless of Claude
Code session state.

Actual behavior

• New terminal windows hang at cursor, no prompt
• Title bar shows bash · -zsh instead of normal shell indicator
• Claude.ai desktop app also fails to open
• Persists until full machine restart
• Shell config files (.zshrc, .zprofile) are unmodified — confirmed clean

Screenshots

(attach your two screenshots here)

Notes

Shell config is minimal and unmodified — this is not a dotfile issue. Claude Code CLI
appears to be leaving orphaned processes or corrupting shared system state that blocks
shell initialization and impacts other Electron-based apps.

<img width="583" height="386" alt="Image" src="https://github.com/user-attachments/assets/0165118a-37e6-4cc3-9651-3bef4e8a7548" />

What Should Happen?

Claude Code sessions should not affect system state outside their own
process. New terminal windows should always open normally, and other applications
(including Claude.ai desktop) should remain functional regardless of whether Claude Code
is running or has recently run.

<img width="583" height="386" alt="Image" src="https://github.com/user-attachments/assets/8cfde809-a5a3-45b8-abd8-9cf3347eeae7" />

Error Messages/Logs

Steps to Reproduce

1. Run a Claude Code CLI session with multiple tool calls (bash commands, file

reads/writes)

1. Open a new Terminal.app window while or after the session is running
2. New terminal hangs — prompt never appears

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Current (as of 2026-04-12)

Claude Code Version

claude-opus-4-6

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Shell config is minimal and unmodified — this is not a dotfile issue. Claude Code CLI
appears to be leaving orphaned processes or corrupting shared system state that blocks
shell initialization and impacts other Electron-based apps.