Claude Fleet Monitor
Enables Claude Code sessions to query fleet status, focus terminals, and manage sessions programmatically via MCP tools.
README
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
/proceven 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-sendalerts 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
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:
| Tool | Description |
|---|---|
fleet_status |
All sessions with summary counts |
fleet_session |
Single session detail by ID or prefix |
fleet_sessions_needing_attention |
Sessions idle over 2 minutes |
fleet_focus |
Focus terminal tab for a session |
fleet_cleanup |
Remove stale ended session files |
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
- Hooks in
~/.claude/settings.jsonfire on session events (start, prompt, tool use, stop, end) - Each hook writes/updates a JSON status file in
~/.claude/fleet/ - Process discovery also scans
/procforclaudeprocesses to find sessions that started before hooks were installed - The TUI monitor, MCP server, and CLI all read these status files
Session States
| State | Meaning |
|---|---|
STARTED |
Session just began |
RUNNING |
Processing a prompt or using tools |
IDLE |
Finished responding, waiting for input |
ERROR |
Turn failed (API error) |
ENDED |
Session closed |
DISCOVERED |
Found via process scan, no hook data yet |
Known Limitations
- Same-name tabs in different windows (Konsole/KDE): When multiple sessions share the same repo name (e.g. two
autofixsessions) 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
| Variable | Default | Description |
|---|---|---|
FLEET_DIR |
~/.claude/fleet |
Directory for session status files |
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.