A local dashboard for inspecting coding-agent traffic: prompts, tool schemas, tool calls, streamed responses, token usage, cost, latency, and request diffs.

I found ccglass while debugging OpenAI-compatible coding-agent traffic. It gives you a local dashboard for the parts that are usually hidden: actual request bodies, system prompts, tool schemas, tool calls, tool results, streamed responses, token usage, cost, latency, and diffs between turns. Useful when an agent calls the wrong tool, sends too much context, breaks on streaming tool calls, or behaves differently across providers. It supports Claude Code, Codex, OpenCode, Qoder, Ollama, LM Studio, OpenRouter, Reasonix, DeepSeek-TUI, and other OpenAI-compatible setups. GitHub: https://github.com/jianshuo/ccglass

I keep running into the same debugging problem with coding agents: when an agent behaves differently than expected, the important part is often hidden in the request/response layer.
Things I usually want to inspect:
- the actual prompt and request body
- tool schemas sent to the model
- tool calls and tool results
- streamed response chunks
- token usage, cost, and latency
- diffs between turns or providers
I found ccglass useful for this because it works as a local dashboard for OpenAI-compatible and coding-agent traffic, including setups like Claude Code, Codex, Qoder, Ollama, LM Studio, OpenRouter, and others.
Curious how others here debug this today. Do you mostly rely on provider logs, custom proxy logging, SDK instrumentation, or a local inspection tool?

ccglass

See what your coding agent sends to the model

See what your coding agent sends to the model

Forum Threads

What do you use to inspect coding-agent traffic?

Forum Threads

What do you use to inspect coding-agent traffic?