I was curious how much RAM Claude Code sessions use, and have visibility over sub-processes it spawns as part of doing its work. I also wanted to experiment with Code Mods, so this felt like a natural little project. Once I saw that a Claude Code session costs 450MB RAM before even starting to do any work, I stopped leaving lingering sessions, and instead close them when I'm done working and start new sessions only when I need it.
I also discovered that closing the terminal tab (using Warp) will not actually close the Claude Code process, and it will stay orphaned in the background consuming RAM until I restarting my dev-container. So now I always close it properly with CTRL+C
I was curious how much RAM Claude Code sessions use, and have visibility over sub-processes it spawns as part of doing its work. I also wanted to experiment with Code Mods, so this felt like a natural little project. Once I saw that a Claude Code session costs 450MB RAM before even starting to do any work, I stopped leaving lingering sessions, and instead close them when I'm done working and start new sessions only when I need it.
I also discovered that closing the terminal tab (using Warp) will not actually close the Claude Code process, and it will stay orphaned in the background consuming RAM until I restarting my dev-container. So now I always close it properly with CTRL+C
Warp team member here. Is "Enable reopening of closed sessions" enabled in your settings? That setting can retain processes for a grace period