[BUG] Claude WSL + Terminal.app become sluggish

Resolved 💬 3 comments Opened Sep 18, 2025 by pinkwerks Closed Sep 25, 2025

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?

Win 11 WSL 2 Debian running in Terminal.app Max plan CC v1.0.117

Some of my conversations start to degrade after time. I can resume some and they seem to keep this degraded response state. When it happens the Claude "thinking" ASCII animation freezes up. If I try and type it becomes buffered and sometimes finally shows up. Exiting killing all user processes and resuming still will encounter it, so it doesn't seem related to time as much as perhaps conversation length or context size. I'm not even going over blowing the 1M stack. Also a top shows me as Claude being the only thing stressing my machine and windows task manager reveals I am not at my machine limits.

I'm attaching a strace of when this occurs.

claude_strace.txt

What Should Happen?

I'd expect to be able to see my input reflected in the terminal immediately when not under system load.

Error Messages/Logs

Steps to Reproduce

I'm afraid I don't have a portable way to repro this. You'd have to resume one of my conversations and see for yourself.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v1.0.117

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗