Integration

Fleet + GitHub: Label-Driven Agent Dispatch from Issues and PRs

Name: Fleet
Author: Fleet

GitHub is Fleet's primary integration. Fleet's watcher daemon polls your repository roughly every two minutes for label changes using the gh CLI. When a ready label appears on an issue, the watcher publishes a fabric event and starts the appropriate agent. That agent creates a branch, does the work, opens a PR, and adds a needs-review label. Reviewers pick that up, and if they approve, a release-manager agent merges and adds a shipped label.

All GitHub access goes through the gh CLI (capped at a 30-second timeout per call) using your existing gh auth login credentials. There are no webhooks and no GitHub App is required. Fleet's merge gate reads PR review decisions and pairs them with fabric approval events: fleet release check <pr> returns mergeable only when a reviewer's pr_approved event (and/or a GitHub APPROVED review decision) is present and not superseded by a later pr_changes_requested. Every decision lands in the fabric event log, giving you an audit trail tied directly to GitHub issues and PRs.

Setup

1

Install the gh CLI and authenticate

gh auth login

2

Install Fleet and initialize your repo

curl -fsSL https://fleetctl.ai/install | sh
fleet init

3

Start the label watcher

fleet watcher start

4

Add a ready label to an issue and watch the agent start

gh issue edit 42 --add-label ready

What you gain

Issues with a ready label automatically dispatch the right agent — no manual task assignment needed
Fleet records every PR, review, and merge decision in the fabric event log, giving you a clear audit trail
The merge gate combines GitHub review decisions with fabric approval events before allowing a merge, so a PR cannot ship without a real reviewer sign-off

Honest limits

Fleet drives GitHub through the `gh` CLI, not the GitHub API directly, so `gh` must be installed and authenticated on the machine running Fleet
Label changes are polled roughly every two minutes; there are no webhooks, so dispatch is near-real-time, not instant
No GitHub App is involved — access is exactly what your `gh` login can do

Frequently asked questions

Does Fleet require a GitHub App or webhooks?

No. Fleet uses the gh CLI with your existing GitHub authentication. There is no GitHub App to install and no webhook endpoint to host — the watcher polls labels roughly every two minutes.

How does the merge gate decide a PR is safe to ship?

`fleet release check <pr>` reads GitHub review decisions and fabric events. It returns mergeable when a reviewer's pr_approved event (or a GitHub APPROVED review) is present and no later pr_changes_requested supersedes it. The output is always JSON.

More integrations

Fleet + Linear →Fleet + Jira →Fleet + MCP (Model Context Protocol) →Fleet + tmux →Fleet + Git Worktrees →Fleet + CI/CD →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet