Claude Code Agent Monitor CLI
A local real-time dashboard for Claude Code and Codex sessions: agent activity and tool calls
- 1,180 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads agent session events through hooks
- Runs a local service with a database
Install
- Works in
Manual install
git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.gitThen run from source via npm per the README.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads agent session events through hooks
- Runs a local service with a database
This is third-party code. Review the repository files before installing.
What it does
The dashboard shows in real time what Claude Code and Codex agents are doing: sessions, subagent activity, tool calls and analytics. It connects to the agents through their built-in hooks, so events arrive as work happens. The UI offers several pages: a dashboard, a kanban board, a sessions list, an activity feed, analytics and workflows. It is built on Node, Express, React and SQLite with WebSocket updates. It installs from source via npm or via Docker and Podman, and the default ports bind to loopback only.
Who it is for. For developers and teams who want visibility into what their Claude Code and Codex agents are doing.
Good fit when
- You want to watch agent sessions in real time
- You need analytics on tool calls and subagent activity
- You want several agents visible on one dashboard
Not a fit when
- You do not need a separate agent observability panel
- You cannot run a local service or containers
Example request
Show on the dashboard which tools the agent called in the last sessionLimitations
It is a standalone service you deploy and keep running, and installation needs Node and Git or Docker. The panel observes sessions but does not control the agents themselves. Data is stored locally in SQLite.
How to disable. Stop the service and remove the hooks from the agent configuration; for Docker run docker compose down.
FAQ
How do events reach the panel?
Through the built-in Claude Code and Codex hooks; a hook handler reads the event and updates the dashboard.
Does data leave my machine?
No, the panel stores data locally in SQLite, and default ports bind to loopback only.
Discussion
No questions or reviews yet.
Related
CLI toolsA dashboard for every Claude Code session on the machine: live agents, cost, history search and MCP tools for Claude.
One browser window for Claude Code, Codex, Gemini CLI and OpenCode: session status, history and requests between agents.
A local dashboard for Claude Code: a live graph of sessions and subagents, tokens, cost and file conflicts.
ClawMetry reads the session files agents already write and shows the timeline, tool calls, tokens and cost in one dashboard.
Hooks for Claude Code and OpenCode draw agent work as a pixel-art office: the main agent as a boss, subagents as employees.
A Claude Code plugin that draws a 3D office where your session and subagents work at desks from real transcripts, zero config.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Code Agent Monitor (this card) | no | 1,180 | |
| Claude Status Bar | no | 732 | a macOS menu bar indicator that shows whether Claude Code is thinking |
| Agenttrail | no | 1,017 | A coding-agent monitor with a project component map and an experimental 3D kitchen view of ongoing tasks |
README in short
The README describes a real-time monitoring dashboard for Claude Code and Codex sessions built on Node, Express, React and SQLite with WebSocket updates. It connects to the agents through their built-in hooks and shows sessions, subagent activity, tool calls and analytics across several pages. Installation is from source via npm or via Docker and Podman, default ports are local, and there is a plugin marketplace for Claude and Codex. MIT licensed.