convez.ai
Agente
hoveychen

claw-fleet

hoveychen/claw-fleet

Ver no GitHub
BomPluginScore · de 0 a 100

Mission control for your Claude Code agents.

Instalação

$npx convez-ai hoveychen/claw-fleet

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
14
Forks
3
Acompanhando
0
Saúde
42%
Último commit
há 1 dia
Versão
v3.2.10
Issues abertas
0
Contribuidores
2

README

A tradução para o português deste README ainda está na fila.

Claw Fleet

Mission control for your AI coding agents. Monitor every session, track token throughput and live USD spend, get AI-generated daily summaries and lessons learned — all from one place. Supports Claude Code, Cursor, OpenClaw, and Codex.

Release License Platform Built with Tauri React TypeScript


What is Claw Fleet?

When you run Claude Code across multiple projects simultaneously — or lean on its multi-agent delegation feature — it's easy to lose track of what each agent is doing, how fast it's working, or whether it's stuck waiting for your input. At the end of the day, you want to know: what actually got done? And what mistakes should your agents avoid next time?

Claw Fleet solves both. It watches session files in real time and presents everything in a clean dashboard. At the end of each day, it generates AI-powered summaries of what your agents accomplished and extracts lessons learned from their mistakes — turning raw session logs into actionable standup reports and persistent knowledge. No server required, no API key needed beyond what Claude Code already uses.

Meet Captain Claw 🦀 — our mascot. A battle-hardened crab commander who keeps every agent in formation.


Supported Agents

Claw Fleet can monitor sessions from multiple AI coding agents:

AgentStatus
Claude CodeFully supported — enabled by default
CursorSupported — opt-in via Settings
OpenClawFully supported
CodexFully supported

Toggle agent sources on or off in the app's Settings panel. Claw Fleet auto-detects which tools are installed on your system.


Why Claw Fleet?


Screenshots


Features

AI daily summaries — the standup update you never write. Each day's sessions are distilled into a narrative: what your agents built, which tasks completed, where they got stuck. Token usage, activity heatmap, tool call breakdown — all generated automatically. Copy as Markdown and paste straight into Slack or your standup thread.

Lessons learned — AI mistakes become team knowledge. Claw Fleet scans session logs for missteps — wrong assumptions, failed approaches, repeated retries — and extracts concise lessons. One click adds them to your CLAUDE.md, so agents never repeat the same mistakes. This is how your fleet gets smarter over time.

8 live statuses, not just "running". Your agents are thinking, executing, streaming, delegating, or waiting for you — Claw Fleet tells you which, with parent-child hierarchies grouped automatically. Stuck agent? Kill it from the dashboard.

Cost tracker that reflects what you actually pay. Token speed tells you how fast an agent is streaming; it doesn't tell you what it's costing you. Claw Fleet shows live USD spend per session on every card, plus a fleet-wide $/min rate chart with a rolling 5-minute window total — fully accounting for cached reads, cache writes, input vs. output pricing, and per-model rates. For a main agent that delegates, you see both its own cost and the aggregate including every subagent it spawned. Catch a runaway loop before it drains your account, and finally know which project is burning your budget.

Security audit built in. Every Bash command your agents run gets scanned and classified by risk. sudo, git push --force, rm -rf — you'll catch the dangerous ones before they become incidents.

Your agents' memory, finally visible. CLAUDE.md files and memory entries scattered across dozens of projects, indexed in one place. Browse, diff, promote to global scope.

Monitor from your phone. The companion Android app connects to your desktop via a secure tunnel — scan a QR code and you're in. See live agent statuses, token speeds, and conversation history from anywhere. Stop a runaway agent from the couch.

Remote agents, local dashboard. SSH into your cloud box and monitor remote agents alongside local ones. Auto-bootstraps itself on the remote side. No port forwarding, no VPN.

Agents that manage agents. Install the Fleet Skill and your AI coding agent can check on — and stop — other running agents on its own.

A CLI for everything. fleet agents, fleet stop, fleet audit, fleet search — all with --json. Stay in the terminal if that's your thing.

Zero config. Download. Open. It reads local session files directly — no server, no API key. macOS, Windows, Linux.


Installation

Download the latest pre-built binary for your platform from the Releases page:

PlatformArchitectureDownload
macOSUniversal (Intel + Apple Silicon)claw-fleet-macos.pkg
Windowsx64 / ARM64claw-fleet-windows-x64-setup.exe
Linuxx86_64claw-fleet-linux-x64.deb · claw-fleet-linux-x64.AppImage
AndroidARM64 / x86_64claw-fleet-mobile.apk

Mobile app: The Android companion app is released separately — look for the latest mobile-v* release on the Releases page. Scan the QR code shown in Claw Fleet Desktop to connect.

Prerequisites

Claw Fleet reads session data written by Claude Code (claude CLI). You need Claude Code installed and have run at least one session before anything shows up.


Build from Source

Requirements

Steps

git clone https://github.com/hoveychen/claw-fleet.git
cd claw-fleet

pnpm install

# Development (hot-reload)
pnpm tauri dev

# Production build
pnpm tauri build

The output binary and installer are placed under target/release/bundle/.


How It Works

Claw Fleet reads directly from Claude Code's local data directory (~/.claude/) — no network calls, no background services, nothing you need to configure.

~/.claude/
├── ide/
│   └── *.lock          ← active IDE process info (pid, workspace, auth token)
└── projects/
    └── <workspace>/
        └── *.jsonl     ← append-only conversation history (one JSON object per line)
  1. Startup — scans all .lock files to find live IDE processes
  2. File watcher — uses OS-native events (FSEvents on macOS, inotify on Linux) to detect new JSONL lines the moment Claude writes them
  3. Status inference — derives session state from the last assistant message's stop_reason field and file modification time
  4. Token speed — aggregates usage.output_tokens across the most recent messages and divides by elapsed time

Everything runs in-process inside the Tauri Rust backend. The React frontend communicates via Tauri's IPC bridge.


Task-as-Unit Mode

Beyond the legacy "spawn a session, watch it" launcher, Fleet supports a higher-level task abstraction where one user-stated goal becomes a DAG of small P-items orchestrated by a long-running master agent (Sonnet 4.6) that dispatches per-P-item worker subprocesses.

Lifecycle:

  1. Inbox — click + New task in the sidebar. Drop files, paste screenshots, or type a description.
  2. Plan — the atomic-plan-tasks skill drafts a DAG of P-items (with touches / depends_on / resources / acceptance / human_gate).
  3. Start — Fleet creates a fleet/<title-slug> git branch and spawns the master session. The master calls fleet task get-dispatchable and dispatches workers respecting resource locks.
  4. Per-item worktree — every dispatched P-item runs inside its own isolated git worktree at ~/.fleet/worktrees/<task>/<p>/ on branch fleet/<task>/<p>. Workers can cargo build / cargo test / pnpm build freely without trampling parallel siblings.
  5. Acceptance audit + fast-forward merge — workers stop on completion; the master verifies acceptance, then mark-done fast-forward-merges the P-item's worktree branch back into the task branch and reaps the worktree. human_gate=true P-items trigger an AskUserQuestion via the Decision Panel before mark-done.
  6. Done — when every P-item is terminal and the master exits, the task flips to Done and completed_at is stamped.

What can you do:

  • Surface every active task in the sidebar (grouped by project) with progress chips
  • See macro metrics per project (active tasks, done this week, avg duration, longest running)
  • Flip manual_review_all on a project to force every P-item through user approval
  • Pause / resume / clear a task — master + workers respond to SIGSTOP / SIGCONT / SIGTERM

Current limits:

  • Fast-forward-only merges; diverged worker / task branches surface as a Conflict and pause the P-item. LLM-driven conflict mediation is the next milestone (see design/task-as-unit-redesign.md §V2).
  • The atomic-plan-tasks skill produces the initial DAG but doesn't iteratively refine it
  • No auto-generated architecture overview — drop one at ~/.fleet/projects/<id>/architecture.md to get Layer-1 context injection
  • E2E mock harness in e2e/task-as-unit.spec.ts exercises the surface; real-agent dogfood lands in the dogfood PR per design/task-as-unit-redesign.md

See design/task-as-unit-redesign.md for the full architecture spec.


Mobile Companion App

Claw Fleet ships with an Android companion app that lets you monitor your agents from your phone.

Features:

  • Live agent statuses with token speed and context usage
  • Conversation history with thinking blocks, tool calls, and code highlights
  • Security audit events
  • Stop agents remotely
  • Dark / light theme, follows system setting

How to connect:

  1. Open Claw Fleet Desktop and click the phone icon in the sidebar (or go to Settings → Mobile)
  2. Click "Enable Mobile Access" — this starts a secure Cloudflare tunnel
  3. Scan the QR code with the mobile app

The mobile app is a read-only client (except for stop commands). All data flows through the desktop app's embedded HTTP server via the tunnel — no direct access to your filesystem.

Building from source: See claw-fleet-mobile/README.md for build instructions.


Contributing

Pull requests are welcome! A few pointers:

  • Backend is Rust in claw-fleet-core/src/ — session.rs owns session parsing, watcher.rs owns the file-system loop
  • Frontend is React + TypeScript in src/ — components use CSS Modules, state is managed with Zustand
  • i18n — locale files live in src/locales/; copy en.json, translate, register in src/i18n.ts

Please open an issue before starting large changes so we can coordinate.

By submitting a pull request, you agree to the Contributor License Agreement (CLA). The CLA grants the project owner the right to relicense contributions under other licenses (including commercial ones) while keeping the public release under AGPL-3.0.


License

This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-only).

Copyright © 2025 hoveychen

Under AGPL-3.0, if you run a modified version of this software to provide a service over a network, you must make the complete source code of your modified version available to users of that service.

Ver o original no GitHub

Bom para

Relacionados