cctracelisted
Install: claude install-skill thevibeworks/cctrace
# cctrace — trace Claude Code's HTTP traffic
cctrace wraps the Claude Code CLI, captures every request/response pair to
`.cctrace/trace-<ts>.jsonl`, and serves a live web UI (requests list,
reconstructed conversation, session replay, cost estimates).
Repo: https://github.com/thevibeworks/cctrace · npm: `@thevibeworks/cctrace`
## Run a traced session
```bash
cctrace # wrap claude, capture everything, open live UI
cctrace -- --continue # everything after -- goes to claude verbatim
cctrace -- -p "explain this" # traced print-mode run
cctrace --mode base-url # lightweight: /v1/messages only, no CA setup
cctrace -s # static: no live server, just files
cctrace --no-open # don't auto-open the browser
cctrace --dir path/to/logs # trace dir (default: ./.cctrace)
cctrace --fresh # don't merge prior traces of a continued session
cctrace --version # print version (+ newer version if known)
cctrace --no-update-check # skip the daily npm version check / prompt
cctrace codex -- exec "..." # trace the OpenAI Codex CLI instead
cctrace grok -- -p "..." # trace the Grok CLI
cctrace kimi # trace the Kimi Code CLI (all non-Claude use mitm)
```
Two gotchas worth knowing before suggesting commands:
- **`-p` position matters**: before `--` it is cctrace's port; after `--` it is
Claude's print mode.
- **A leading `--` is eaten by b