kunchenguid /firstmate

Talk to one agent. Ship with a crew.

★ 8,900⑂ 2,761👁 28⑃ 6,909● 1,557▤ 0
ShellMITCreated 2026-06-12
More from this author
+15
Daily
8,900
stars
2,761
forks
28
watchers
6,909
prs
1,557
issues
0
releases

README

firstmate

  
  
  


Talk to one agent. Ship with a crew.


  


 What it is

You can run one coding agent easily.
But the moment you want three project tasks done in parallel - fixes, investigations, plans, audits - you become a tab-juggler: babysitting sessions, copy-pasting context between repos, forgetting which terminal had the failing test.

firstmate flips the model.
You talk to a single agent - the first mate - and it runs the crew for you: spawning autonomous agents in a visible session backend, giving each a clean git worktree, supervising them to completion, and handing you finished PRs, approved local merges, or standalone investigation reports.
For larger fleets, you can opt in to persistent secondmates: second mates that are still ordinary direct reports, but run from their own isolated firstmate homes on this machine or another SSH-reachable host.

firstmate is not a model, not a harness, not a skill, not an MCP server, and not a CLI.
firstmate is an agent distro for running a crew of agents.
An agent distro is a portable directory of instructions, skills, tooling, policies, and state conventions that turns a general-purpose agent into a specialized one.
There is no app to install: the cloned repo is the distro - AGENTS.md, bundled firstmate skills, and helper scripts that any terminal coding agent can follow.
Launching a supported harness inside it for your primary session instantiates your first mate - and makes you the captain.

 Features

- One liaison - you talk only to the first mate; it dispatches, supervises, escalates only real decisions, and reports plain outcomes.
- A visible crew - every crewmate works in its own tmux window or Herdr tab, or in an experimental Zellij tab, experimental cmux workspace, experimental Tern block, experimental Orca terminal, or experimental T3 Code thread you can watch or interact with; the first mate reconciles.
- Disposable worktrees - each task runs in a clean treehouse git worktree, or an Orca-managed worktree when backend=orca, so parallel work on one repo never collides.
- Two task shapes - ship tasks deliver authorized changes; scout tasks leave standalone investigation reports when the intake contract warrants separate research.
- Explicit project modes - each project ships via no-mistakes, direct-PR, or local-only, with an optional +yolo merge-autonomy flag, an optional branch= override for the default fm/ ship-branch prefix, and an optional forge=gerrit binding under which the worker publishes a Gerrit change instead of opening a pull request, plus an optional pr=manual token under which the worker writes the PR title and body instead of the pipeline.
- Self-repo boundary - a home runs as firstmate user/operator by default, so a firstmate bug is diagnosed and patched locally but never pushed, PRed, issued, commented, or forked upstream on its own; publishing to firstmate's own repository needs the config/firstmate-role maintainer opt-in or a per-task captain consent (schema).
- Opt

Top issues

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON