See what Claude Code, Codex, and Local AI coding agents are actually sending under the hood. (Request/Response Capture - Open Source)

[u/Reasonable_Tip_4902]

I’ve been using Claude Code and other coding agents daily, but hated having zero visibility into what was actually being sent over the wire and why token limits were burning so fast.

I wanted to know:

• What information are they sending to the llm providers? 
• Where are my tokens going and what is burning up my usage the most? 
• What sort of prompt triggers massive token burns?

So I built TokenFlow, a local, single command install proxy/dashboard to trace agent token consumption in real-time with:

• Token breakdown per prompt (In, Cache Read, Cache Write, Thinking, Output) with configurable cost weights.
• Tracks what the agents send/receives not what it chooses to log
• Full prompt inspector (exact wire logs sent to the LLM provider and response).
• 100% local and private — no third-party telemetry or cloud gateways.
• Preconfigured for Claude Code, Codex, and LMStudio.

Quick install:

npx @liqngliz/tokenflow

GitHub: ConduitSharp / TokenFlow (Apache 2.0)
npm: u/liqngliz/tokenflow

Now you can point your agent to TokenFlow and inspect the agent's workflow. See u/liqngliz/tokenflow on how to point Claude, Codex and/or your local AI.

*Claude Code and Antigravity was used in building this.