Tuesday, January 6, 2026
Claude Code performance issues
Users are reporting performance issues like overheating and high memory usage when using Claude Code, particularly within editors like Cursor, leading some to switch to alternatives.
welcome to advent of claude every day i will build a new ui on top of the claude code sdk jsonl format #1 - tmux vibes + parallel subagents - simple chronological display
It’s nothing crazy. I had 3-5 windows open in cursor and even my MacBook Pro heated like insane (esp w docker running). Most of my memory was taken by Cursor so I just switched it out for Claude code. The current setup: Ghostty, Claude code and Neovim I split screen three ways
I completely agree. If you're using Claude Code, it's better to avoid using the internal terminals of VSCode or Cursor. With Ghostty, there’s no flickering or garbled text, and you can see that it’s smooth and snappy to use. I wonder how people on Windows are handling