agent-monitor

Monitor Claude Code sub-agent activity with a TypeScript CLI.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/victorstein/claude-canvas --skill agent-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-monitor
Source: https://github.com/victorstein/claude-canvas/tree/main/canvas/skills/agent-monitor
Command: npx skills add https://github.com/victorstein/claude-canvas --skill agent-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Real-time visibility into Claude Code sub-agent activity to simplify debugging, auditing, and coordination within a tabbed terminal interface.

Core Features & Use Cases

  • Tabbed interface with one tab per sub-agent
  • Scrollable output streams, tool call display, and git diff visualization
  • Auto-spawn when any sub-agent starts and per-session state tracking
  • Use cases: debugging agent workflows, monitoring concurrent tasks, auditing tool usage in Claude Code

Quick Start

Show the agent monitor in the current terminal: bun run src/cli.ts show agent-monitor --scenario monitor Spawn the agent monitor in a new WezTerm/tmux pane: bun run src/cli.ts spawn agent-monitor --scenario monitor With initial configuration: bun run src/cli.ts spawn agent-monitor --scenario monitor --config '{"parentSessionId": "session-123","agents":{}}'

Frequently Asked Questions about agent-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor Claude Code sub-agent activity in real time?

You can monitor Claude Code sub-agent activity in real time by spawning a tabbed terminal interface that tracks per-agent state, output streams, and tool calls. This provides live visibility to support debugging and auditing concurrent agent workflows.

How do I track tool calls and git diffs across multiple sub-agents?

Tracking tool calls and git diffs across sub-agents requires a monitor with per-session state tracking and a tabbed interface. Each tab displays scrollable output streams, tool call details, and git diff visualizations for individual agents.

Can I auto-spawn a terminal monitor when a sub-agent starts?

Yes, you can auto-spawn a terminal monitor when a sub-agent starts using hook-based auto-spawning. This automatically launches the monitoring interface in a new WezTerm or tmux pane whenever sub-agent activity begins.

Does the agent monitor support multiple concurrent sub-agent sessions?

Yes, the monitor supports multiple concurrent sub-agent sessions through per-session state tracking. You can configure initial sessions by passing a JSON config with a parent session ID and agent mapping when starting the CLI.

How do I start the sub-agent monitor in my current terminal?

You start the sub-agent monitor in your current terminal by running the TypeScript CLI show command with the monitor scenario. This displays the tabbed monitoring interface directly in your existing terminal session.

What are the limitations of monitoring Claude Code sub-agent workflows?

Monitoring Claude Code sub-agent workflows relies on a TypeScript CLI and hook-based auto-spawning, requiring a compatible terminal environment like WezTerm or tmux. It is designed for safe operation but depends on terminal UI support for tabbed interfaces.