Agent Fleet

What Agent Fleet does

Agent Fleet is a local swarm of scoped Cursor agents that work on your git repositories. It is built on the Cursor SDK, and each agent is a Composer session with limited paths, MCP servers and multi-phase runs. Work is dispatched from a CLI, from Python or from GitHub issue comments, and the repository description lists Hermes integration among its features.

A dispatcher runs up to max_parallel agents, isolating same-repo tasks in git worktrees. A code_review pipeline runs implement, scope, verify and reviewer steps, ending in an approve, request_changes or block verdict. A two-pass PR analyzer works from the CLI or a GitHub Action, and background modes include a PR loop watcher, issue-comment dispatch and cron schedules. Personas are markdown prompts with optional path allowlists, and runs are logged as JSONL under ~/.agent-fleet. The default model is composer-2.5.

Key features

• Parallel Composer agents with git worktree isolation
• code_review pipeline ending in approve, request_changes or block
• Two-pass PR analyzer for the CLI and GitHub Actions
• PR loop watcher, issue-comment dispatch and cron schedules
• Personas as markdown prompts with path allowlists
• JSONL run logs

When to use it

• Fixing backend, frontend and test code in different packages at the same time
• Reviewing agent-written changes before they are merged
• Letting a watcher dispatch fix agents until CI passes on a pull request

Who it is for: Developers who use Cursor agents and want parallel, reviewed changes across their git repositories.

How it fits with Hermes Agent

The repository description lists Hermes integration, but the agents themselves are Cursor Composer sessions; it is not built only for Hermes Agent.

Requirements: Python 3.14, a Cursor API key and a git workspace

Note: It needs a Cursor API key and Python 3.14, and the README documents Cursor Composer agents rather than Hermes Agent.

FAQ