This is amazing except for a few issues, I hope there is some session memory coming.
Environment
Note: I’m relatively new to working in WSL, and Claude CLI was functioning without issue when I first started using it. The hanging behavior began recently. I haven’t significantly changed my setup, so I’m unsure if this is a regression, a WSL-related compatibility issue, or something environmental.
Bug Description
Claude CLI intermittently hangs during usage in WSL. It starts fine and responds to input, but at a random point in the session, it will stop responding entirely. The process remains running, but no output is returned, and no error message is shown. This issue is disruptive and makes it difficult to maintain consistent workflows.
Steps to Reproduce
- Start a Claude CLI session inside WSL (Ubuntu 22.04) via the VS Code terminal.
- Begin a normal interaction — requesting code, asking questions, etc.
- After a few prompts, Claude suddenly stops responding.
- Run pkill on the Claude CLI process — this temporarily fixes the issue.
- Start a new session — the issue will usually return after some time.
- Occasionally, multiple Claude processes are found running simultaneously in the background.
Expected Behavior
Claude CLI should maintain consistent responsiveness throughout the session. If the session ends, times out, or encounters an error, it should return a message or log rather than silently hanging.
Actual Behavior
- Claude responds normally for the first few prompts.
- Then it suddenly stops responding, without logging any error or ending the session.
- Running pkill on Claude CLI temporarily resolves the issue.
- Multiple Claude CLI sessions are sometimes left running in the background.
- The issue occurs intermittently and unpredictably, even after restarting WSL, rebooting, or reinstalling the CLI.
Additional Context
- I’ve tried rebooting WSL, restarting VS Code, reinstalling the Claude CLI, switching networks, and limiting session complexity — none have resolved the issue.
- I didn’t have this problem early on; it appeared only after some time using WSL.
- A clearer error message, timeout warning, or a self-healing session process would be extremely helpful.
- I’m happy to provide logs, CLI output, or run test scenarios to help diagnose.
This is amazing except for a few issues, I hope there is some session memory coming.
Environment
Platform (select all that apply):
Claude CLI version:
Host OS: Windows 11
WSL Distro: Ubuntu 22.04
Terminal: VS Code integrated terminal (running in WSL)
Bug Description
Claude CLI intermittently hangs during usage in WSL. It starts fine and responds to input, but at a random point in the session, it will stop responding entirely. The process remains running, but no output is returned, and no error message is shown. This issue is disruptive and makes it difficult to maintain consistent workflows.
Steps to Reproduce
Expected Behavior
Claude CLI should maintain consistent responsiveness throughout the session. If the session ends, times out, or encounters an error, it should return a message or log rather than silently hanging.
Actual Behavior
Additional Context