ccglass

What does this agent do, and when should you use it?

ccglass is a local logging reverse-proxy with a web dashboard for observing the real requests made by coding-agent CLIs. It redirects traffic by setting the client's base-URL environment variable (e.g. ANTHROPIC_BASE_URL, OPENAI_BASE_URL); the client still performs its own HTTPS to the real API, so no CA certificates are needed and TLS pinning is avoided. The dashboard shows the full system prompt, tool schemas, message history, token/cache/cost numbers, a turn-to-turn diff, and a sequence diagram of the agent loop. Supported clients include Claude Code, Codex, DeepSeek-TUI, Reasonix, CodeBuddy, Kimi, and OpenCode, with upstreams spanning Ollama, LM Studio, OpenRouter, AWS Bedrock, and Google Vertex AI. For clients with hardcoded upstream URLs (like Tencent's CodeBuddy), it offers a forward-proxy mode with targeted TLS MITM. Captures are stored content-addressed (git-style) under ~/.ccglass/sessions/ with auth tokens masked by default. It installs globally via npm or Homebrew and starts with a single command.

Running ccglass (or ccglass claude, ccglass codex, etc.) starts a local proxy, points the client at it via the right base-URL env var, launches the client, and opens a dashboard at http://127.0.0.1:<port>. The dashboard provides: a live request stream (expandable system prompt, messages, tools), an agent-loop sequence diagram pairing tool_use and tool_result by call_id with color coding, a turn-to-turn diff highlighting added context and cache breakpoints, exact token/cache-hit/cost numbers from response usage, streamed SSE reassembled into final messages, export to raw HTTP / Markdown / JSON / HAR, session summaries, per-request latency with trend sparklines, Copy as cURL replay, light/dark themes, and optional MCP self-inspection (registers query tools into Claude Code so the agent can inspect its own requests; disable with --no-mcp). Captures go to ~/.ccglass/sessions/<project-path>-<hash>/ in content-addressed format with authorization and x-api-key masked; ccglass view reopens saved logs, ccglass migrate copies legacy ./.ccglass data into the global store, and ccglass export dumps a specific request. For CodeBuddy, whose upstream copilot.tencent.com is hardcoded, ccglass codebuddy runs a forward proxy intercepting HTTP CONNECT tunnels with targeted TLS MITM and an auto-generated local CA.

1. An engineer debugging agent prompts who suspects Claude Code's system prompt or tool list differs from expectations and wants to read the raw request each turn.
2. A team controlling API spend that needs per-request token, cache-hit-rate, and estimated USD figures to see where a session's cost comes from.
3. A developer investigating context bloat, using the turn-to-turn diff to see exactly which blocks were added this turn and where cache breakpoints land.
4. A user of local or third-party models who inspects OpenAI-compatible clients via ccglass ollama, lmstudio, openrouter, or glm providers.
5. A Tencent CodeBuddy user whose built-in models hardcode copilot.tencent.com and therefore require the forward-proxy mode (HTTP CONNECT + TLS MITM).
6. An IDE user (Cursor BYOK, Cline, Continue.dev) who runs ccglass proxy and points the IDE's API base URL at the proxy address to observe requests.

How do you install or deploy this agent?

Requires Node.js >= 18. Install with either:

npm install -g ccglass

or:

brew install jianshuo/tap/ccglass

How do you use this agent?

Basic usage:

ccglass            # interactively pick a client to inspect
ccglass claude     # inspect Claude Code (args pass through, e.g. --resume)
ccglass codex      # inspect Codex (API-key mode required; ChatGPT login uses WebSocket and bypasses the proxy)
ccglass kimi       # Claude Code to Moonshot; set ANTHROPIC_AUTH_TOKEN
ccglass codebuddy  # forward-proxy mode; set "http.proxy": "http://127.0.0.1:9999" and "http.proxyStrictSSL": false in your IDE

Each client needs its own credentials (OPENAI_API_KEY, DEEPSEEK_API_KEY, Zhipu's OPENAI_API_KEY, etc.). Generic escape hatch for any client:

ccglass run --upstream https://my.custom.api/v1 --env-var MY_CUSTOM_BASE_URL -- my-tool

Proxy-only mode for IDEs:

ccglass proxy --provider openai

Other commands: ccglass view (reopen dashboard over saved logs), ccglass usage (token + USD rollup), ccglass export <session>/<seq> --format raw|md||har, ccglass migrate, ccglass rm <session>. The dashboard runs at a URL like http://127.0.0.1:57633; press Ctrl-C to stop.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?