@jianshuo: Only when you can see it can you talk about understanding. I wrote ccglass; install it via npm and you can see what Claude Code is secretly sending to the large model—system prompts, 48 tools, token accounts—all laid out.

– | any client | per provider | per provider | per provider | Kimi runs through Claude Code against Moonshot's Anthropic-compatible endpoint — make sure your Moonshot key is set (ANTHROPIC_AUTH_TOKEN). DeepSeek-TUI uses its OpenAI-compatible Chat Completions endpoint — make sure your DeepSeek key is set (DEEPSEEK_API_KEY). ## What you get - **Live request stream** — every call appears instantly; click to expand the system prompt, messages, and tools with all escaped strings unescaped. - **Turn-to-turn diff** — pick two requests, see exactly what context was added this turn and which blocks carry a cache breakpoint. - **Token / cache / cost** — exact input/output/cache tokens from the response usage, cache-hit rate, and estimated USD per request (per-provider pricing). - **Response reassembly + export** — streamed SSE rebuilt into the final message (stop_reason, tool calls, usage), for both the Anthropic and OpenAI wire formats; export any request to Markdown / JSON / HAR. ## Usage ``bash ccglass # pick a client interactively ccglass claude [args...] # inspect Claude Code (args pass through, e.g. --resume) ccglass codex [args...] # inspect Codex ccglass deepseek [args...] # inspect DeepSeek-TUI (dispatcher) ccglass deepseek-tui [args...] # inspect DeepSeek-TUI runtime directly ccglass kimi [args...] # inspect Kimi (via Claude Code) ccglass run --provider openai -- # inspect any client ccglass view # re-open the dashboard over saved .ccglass/ logs ccglass export --format md|json|har `` ### Options | Flag | Default | Meaning | |---|---|---| | –provider

| from command | Force format/env forrun (claude/codex/deepseek/kimi/openai) | | –upstream | per provider | Override the upstream API | |–port | auto | Dashboard port | |–proxy-port | auto | Proxy port | |–dir |./.ccglass| Where logs are stored | |–open| off | Open the dashboard in your browser | |–no-redact| off | Keep auth tokens unmasked in saved logs | ## Logs & secrets Captures are written to./.ccglass//NNNN.json. Auth tokens (authorization, x-api-key) are **masked by default** — pass –no-redactto keep them. Treat the log directory as sensitive regardless. ## Requirements Node ≥ 18. No runtime dependencies. ## Acknowledgments Heartfelt thanks to **庄表伟 (@zhuangbiaowei (https://github.com/zhuangbiaowei))** for contributing **first-class DeepSeek-TUI support** (#1 (https://github.com/jianshuo/ccglass/pull/1)). DeepSeek-TUI ships as a dual-binary coding agent — adeepseekdispatcher and adeepseek-tuiruntime. 庄表伟 wired up both as native ccglass providers, pointing them at the proxy viaDEEPSEEK_BASE_URL` and reusing the existing OpenAI-compatible Chat Completions adapter, so every DeepSeek request now shows up in the dashboard with zero extra setup. The contribution also added them to the interactive picker, documented usage across the README, and shipped provider regression tests to keep it working. Thank you for making ccglass better for the whole DeepSeek community. 🙏 ## License MIT