Been using claude code daily for months. I am someone who just run it on --dangerously-skip-permissions . Recently started logging all the requests going out and some of it surprised me. (Through a proxy on my local laptop)
Files I didn’t explicitly mention were showing up as context. I guess this was expected because it needs to know, but a ton of other metadata files are also included. A .env file was included in one request because it happened to be in the same directory. Later I explicitly block using .gitignore. Also, it uses a ton of other context in the background when it sends all the queries, like a lot of summarized versions of files and code snippets. I had no idea until I started capturing the actual request bodies.
Most of us stuff, I realized the caching is sometimes turned on and turned off. This is really bad, especially for someone who always uses Claude code, and the caching is only for 5 min. I would rather prefer having a caching of 1 h on Claude code by default. I’m thinking of having a proxy that will change this parameter in the body every time when I use Claude code.
Also the cost breakdown was different from what I expected. A few long sessions were eating way more than I realised. And the claude pricing model will eat my quota faster than ever.
And also there is one huge session with one token, one output token in the first, which takes all your files and sends it to the claude haiku. It’s a little bit notorious, and I’m really concerned. I don’t know what Claude is actually doing here.
Curious if others have looked into this. What do you use to monitor what’s actually going out?
submitted by
/u/AssociationSure6273
Originally posted by u/AssociationSure6273 on r/ClaudeCode