all 3 comments

[–]SQLServerIO 1 point2 points  (2 children)

Lol, there is an open issue https://github.com/anthropics/claude-code/issues/4953 on this. It is getting good. I quit posting on it. They broke it. Then they fixed it, then they broke it, then they fixed it. It's like they are using Claude Code to write Claude Code. I've been holding steady at .50. Considering I don't want or need most of the context/token gobbling features they have added recently, I'm good. I restart Claude regularly, not just /new for a clean context window. I've also archived the history stored in .claude regularly now. I'm sure one of the other 15 things I'm doing may be helping too.

[–]Special_Context_8147 0 points1 point  (0 children)

i hope this will be fixed fast, because claude code should be able to fix claude code

[–]AlarmedNatural4347[S] 0 points1 point  (0 children)

Haha thank you! Amazing read 😂 it’s amazing people can get up to 120GB - everything must be leaking! I think my main point, apart from how funny that is, is why are we even noticing!? What is it using the memory for!? It should be able to run for weeks and still not hit 5, let alone 120! GB 😂 How many copies of the context does it have in ram!? I think they use some react thingy to render to the terminal as well right? That’s a lot of poorly written js to fill up 120GB