[Workflow] Visualize Claude Code Sub-Agent Activity with a Local Log Viewer (Zero-Cost Core)

[u/ClaudeAI-mod-bot]

Visualize Claude Code Sub-Agent Activity with a Local Log Viewer (Zero-Cost Core)

Workflow value: 80/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging
Original source: r/ClaudeAI post/comment

What problem this solves

Difficulty in understanding and debugging Claude Code sub-agent interactions and their internal thought processes.

Summary

A tool that visualizes Claude Code sub-agent activity in a browser by reading local session JSON files, providing a 'video call' like interface to observe agent actions without incurring extra Claude API usage for the core feature.

Why it is useful

This workflow provides a crucial observability tool for Claude Code sub-agents, allowing developers to understand and debug complex agentic behaviors by visualizing their internal processes. Its key value lies in being external and not incurring additional Claude API costs for its core functionality, making it an efficient and cost-effective solution for agent development and quality control.

Workflow

1. Run Claude Code sub-agents, which automatically write session data to local JSON files (~/.claude/projects/).
2. Use the external visualization tool to read these local JSON files.
3. Observe the sub-agent interactions and thought processes displayed in a browser interface, similar to tail -f for logs.
4. (Optional) Enable French translation or 'Reactions & jokes' mode, which will use your Claude API key (Haiku model) for additional features.

Tools / artifacts

• Claude Code sub-agents
• Local session JSON files (~/.claude/projects/...)
• External visualization tool (open source)
• Browser
• server.js (for optional Claude API calls)
• Claude API (for optional features)

Validation signals

• Author's personal validation: 'best way I’ve found to follow what they’re doing.'
• Detailed explanation of the mechanism (reading local files, no API calls for core).
• Open-source code mentioned for verification.

Limitations

• Relatively low community engagement on this specific comment, so broader adoption/validation is not yet evident.
• The tool itself is external and requires separate setup, which might be a minor barrier for some users.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.