[BUG] v2.1.233 Windows: Claude Code silently exits immediately after Bash tool dispatch in a long/resumed session

Preflight Checklist

• [x] I searched existing issues and did not find an open report with this exact v2.1.233 Bash-dispatch reproduction.
• [x] This report covers one failure mode: the Windows CLI process silently exiting during tool dispatch.
• [x] I am using the latest Claude Code version available on this machine.

What's Wrong?

On Windows 11, Claude Code 2.1.233 silently exits immediately after dispatching a Bash tool call in a long/resumed interactive session.

The UI shows the Bash call as Running..., then claude.exe disappears and control returns to the parent PowerShell prompt:

Bash(...)
  Running...

PS D:\Modex>

This is a process exit rather than an ordinary hang. The old TUI remains visible because the terminal state is not restored.

Forensic inspection of the session JSONL shows that the final event is:

assistant -> tool_use Bash

There is no corresponding tool_result, tool error, assistant response, or graceful shutdown record after it.

What Should Happen?

The Bash command should complete and return a tool_result. If the subprocess cannot be launched or fails, Claude Code should display a structured error and keep the REPL alive. Terminal modes should be restored on every exit path.

Error Messages / Logs

There is no visible error, panic, stderr output, or Windows Application Error Event ID 1000 for the exit.

The affected transcript ends at the Bash dispatch:

2026-08-15 18:22:32  assistant  tool_use Bash
<end of transcript; no matching tool_result>

In an earlier occurrence, the debug log showed a successful shell snapshot and then ended after the shell-spawn path, including:

Spawning shell without login (-l flag skipped)

No subsequent Bash result or crash message was logged.

Steps to Reproduce

This is recurrent in the affected long session, but I do not yet have a small deterministic reproduction:

1. Open Windows Terminal with a PowerShell host.
2. Start or resume a long-running Claude Code session.
3. Continue using tools over an extended period.
4. Have Claude dispatch a Bash command that launches a Python executable using Windows paths.
5. The Bash tool displays Running....
6. claude.exe silently disappears and the terminal returns to the parent PS> prompt.

Affected-session characteristics:

• Session duration: approximately 3 hours
• JSONL transcript size: approximately 2.2 MB
• Total tool calls: approximately 184
• Bash tool calls: approximately 119
• PowerShell tool calls: 1

Control Tests

• Git Bash runs successfully by itself.
• The same Python probe command that was pending at the crash point completes successfully with exit code 0 when run directly outside Claude Code.
• A short fresh-session Bash probe can succeed, so Bash is not universally unavailable.
• Disabling the Bash tool did not resolve the overall process-exit behavior: one earlier run also exited after a PowerShell tool dispatch. This may indicate a shared Windows subprocess/console-host problem, although Bash dispatch is the clearest and recurrent trigger in the affected session.

Environment

• Claude Code: 2.1.233
• Install method: npm global package
• OS: Windows 11 Home, 10.0.26100
• Terminal: Windows Terminal 1.24.11911.0
• Host shell: PowerShell
• Git for Windows: 2.45.2.windows.1
• Node.js: 24.14.0
• npm: 11.9.0
• CPU: AMD Ryzen 9 8945HX
• RAM: 32 GB
• A third-party API-compatible endpoint/model override is configured; endpoint and credentials are omitted from this public report.

Workarounds Tested

• Temporarily denying Bash and using the PowerShell tool: the process still exited during a later PowerShell dispatch.
• BUN_JSC_useFTLJIT=0: a short Bash probe succeeded. However, the crash shown above occurred in a Claude process that had already been started before this environment variable was configured, so this occurrence does not establish whether the JIT workaround fixes long/resumed sessions.
• Executing the same probe outside Claude Code: succeeds with exit code 0.

Additional Information

The full JSONL transcript, debug logs, and any future crash dump may contain source code, project paths, API configuration, or credentials, so they are not attached publicly. Sanitized excerpts or a dump can be provided privately if maintainers request them.

Potentially related:

• #46015 — Windows Git Bash crash after shell snapshot/spawn
• #51464 — Windows native/Bun segmentation faults and JIT workaround
• #51620 — Windows silent CLI exits
• #55424 — Windows REPL silently exits during long-running sessions with dense Bash subprocess use
• #83793 — Windows crash leaves terminal mouse-tracking state corrupted
• #86961 — v2.1.233 Windows crashes without useful Windows logs