ClaudeMon

Monitor your Claude Code sessions in real time

See what every agent is doing across machines and branches. Detect file conflicts before they happen. Know when Claude needs your input.

Open source | Self-hostable | Zero persistent storage

Open Dashboard npx claudemon-cli init Copied

app.claudemon.com

ClaudeMon | Monitor your Claude Code sessions in real time

2 active 1 waiting LIVE

Agent Map 3 sessions

dev-machine local 3

claudemon main 2 sessions

a3f2b8c1 4m 12s Working

main 3 edits · 6 cmds

Edit src/index.ts

b7d2e914 1m 45s Thinking

feat/api 1 edit · 3 cmds

vector-seo main 1 session

c4e9a1f0 2m 33s Waiting

main 5 edits · 2 cmds

Claude needs your input

x a3f2b8c1 bypass claudemon opus-4-6

. Read store.ts 85 lines 4m ago

~ Edit index.ts +5 -2 3m ago

>_ Bash npm run build 0 errors 2m ago

? Grep /handleEvent/ 1m ago

~ Edit wrangler.toml +1 -1 30s ago

. Read relay.test.ts 158 lines just now

Activity 0 events

a3f2b8 . Read store.ts 4m

a3f2b8 ~ Edit index.ts 3m

a3f2b8 >_ Bash npm run build 2m

a3f2b8 ? Grep /handleEvent/ 1m

a3f2b8 ~ Edit wrangler.toml 30s

a3f2b8 . Read relay.test.ts now

b7d2e9 >_ Bash npm test 1m

c4e9a1 ?! Notify needs input 2m

Conflicts 1

src/index.ts

a3f2b8c1 b7d2e914

Both editing

What you get

Everything updates over WebSocket. No polling, no refresh.

Agent Map

Live topology of all Claude Code sessions. See status, branch, project, and current tool call at a glance. Sessions across machines, worktrees, and cloud instances.

Live Activity

Real-time stream of every tool call, edit, bash command, and search. Click into any session for the full timeline with inline diffs and syntax-highlighted output.

Conflict Detection

Automatic detection when multiple sessions edit the same file. Catch merge conflicts before they happen. Real-time alerts when agents step on each other.

How it works

Three steps. Under a minute.

Install the hook

Run npx claudemon-cli init. It adds a lightweight async hook to your Claude Code settings. Under 50ms overhead, non-blocking.

Use Claude Code normally

Every tool call, edit, and command fires an event to the ClaudeMon relay. Events are ephemeral -- no persistent database, no data retention.

Watch the dashboard

Open app.claudemon.com to see all your sessions in real time. WebSocket-powered, instant updates.

Privacy-first architecture

No tracking, no accounts, no data retention.

Ephemeral relay

No persistent database. Events live in Durable Object memory and auto-purge after 1 hour of inactivity.

You control what's sent

The hook sends tool metadata including file paths, tool names, and inputs. Review the open-source hook script to see exactly what data flows through.

Self-hostable

Run your own ClaudeMon instance on Cloudflare Workers. One command deploy, zero ongoing cost on the free tier.

Open source

Every line of code is on GitHub. Audit the hook, the relay, and the dashboard yourself.

FAQ

No. ClaudeMon only receives tool metadata: tool names, file paths, session IDs, and timestamps. File contents, conversations, and environment variables are never sent.

Yes. ClaudeMon runs on Cloudflare Workers with Durable Objects. Clone the repo, run wrangler deploy, and point the CLI at your own instance. It fits within Cloudflare's free tier.

No. The hook fires asynchronously and adds under 50ms of non-blocking overhead. Claude Code never waits for ClaudeMon to respond.

All 27 Claude Code hook events: SessionStart, SessionEnd, tool use events (PreToolUse, PostToolUse), notifications, permission requests, context compaction, subagent lifecycle, and more.