A request monitoring system for Claude Code that captures and visualizes all API requests and responses in real time....
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 57/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if cc-viewer belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/weiesky/cc-viewer && cd cc-viewer && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf cc-viewerNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ cc-viewer/ ← clones here
A request monitoring system for Claude Code that captures and visualizes all API requests and responses in real time. Helps developers monitor their Context for reviewing and debugging during Vibe Coding.
Source: GitHub repository
Source check: October 19, 2026
Upstream commit: October 16, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.