Claude Fleet Monitor

Fleet monitoring for Claude Code sessions. See all your running sessions at a glance, get notified when one needs input, and jump to the right terminal tab instantly.

Features

• TUI Dashboard -- live view of all Claude Code sessions with status, detail, and age

• Process Discovery -- finds running sessions via /proc even before hooks fire

• MCP Server -- any Claude session can query fleet status programmatically

• Terminal Focus -- switch to a session's Konsole tab (or raise its window on other terminals) by name or PID

• Desktop Notifications -- notify-send alerts when a session has been idle for over 2 minutes

• Hooks Integration -- Claude Code hooks emit real-time status (running, idle, error) as sessions interact

Related MCP server: mcp-terminal-server

Install

pip install claude-fleet-monitor
claude-fleet install

Or install from source:

git clone https://github.com/andre-motta/claude-fleet-monitor.git
cd claude-fleet-monitor
pip install .
claude-fleet install

Restart your Claude Code sessions after the first install to activate hooks.

Upgrading

pip install --upgrade claude-fleet-monitor

No need to re-run claude-fleet install or restart sessions. Hooks and MCP server point to pip-installed entry points, so upgrades take effect immediately.

Dependencies

• python3 >= 3.10

Optional:

• qdbus -- Konsole tab switching (KDE)

• xdotool -- generic window focus (X11)

• notify-send -- desktop notifications

Usage

TUI Dashboard

claude-fleet monitor              # default 2s refresh
claude-fleet monitor --refresh 5  # 5s refresh

Or run the script directly:

~/.claude/bin/fleet-monitor.sh

Focus a Session

claude-fleet focus autofix         # by repo name
claude-fleet focus 2467709         # by PID
claude-fleet focus proc-2467709    # by session ID

On Konsole: switches to the exact tab. On other terminals: raises the window.

Quick Status (no TUI)

claude-fleet status

MCP Tools

Any Claude Code session with the fleet MCP server can use these tools:

Just ask Claude: "what sessions are running?" or "focus on the autofix session".

How It Works

Claude Code Session A --\                                      <-- MCP server
Claude Code Session B ---|-- hooks --> ~/.claude/fleet/*.json  <-- TUI monitor
Claude Code Session C --/                                      <-- fleet-focus

1. Hooks in ~/.claude/settings.json fire on session events (start, prompt, tool use, stop, end)

2. Each hook writes/updates a JSON status file in ~/.claude/fleet/

3. Process discovery also scans /proc for claude processes to find sessions that started before hooks were installed

4. The TUI monitor, MCP server, and CLI all read these status files

Session States

Known Limitations

• Same-name tabs in different windows (Konsole/KDE): When multiple sessions share the same repo name (e.g. two autofix sessions) and live in different Konsole windows, the focus command will switch to the correct tab but may raise the wrong window. Workaround: keep same-name sessions grouped in the same Konsole window.

• Wayland window activation: On Wayland/KDE, window raising uses KWin scripting via DBus. Other Wayland compositors may not support programmatic window activation.

Configuration

Environment Variables

Uninstall

claude-fleet uninstall              # removes everything including data
claude-fleet uninstall --keep-data  # keeps ~/.claude/fleet/

Publishing

This project uses trusted publishing via GitHub Actions. To release:

git tag v0.1.0
git push origin v0.1.0

The workflow builds and publishes to PyPI automatically.

License

MIT