mship¶
A structured interface between AI coding agents and a running multi-repo
system. mship owns the coordination an agent is bad at — isolated worktrees per
task, dependency-ordered tests and PRs across repos, a running stack with
healthchecks — and exposes it all as structured state instead of shell
guesswork. You (or your phone) steer; the agent builds; nothing lands on main
by accident.
Pre-1.0. API may change. Pin a commit if you need stability.
Start here¶
Getting started — install, create a workspace, and take one task from spawn to a merged PR. Ten minutes, the whole loop.
uv tool install git+https://github.com/atomikpanda/mothership.git
Guides, by goal¶
- Ship a feature — the spec-first loop: design agreed, plan written, gates enforced.
- Fix a bug — the shortest safe path to a merged
fix (and the
--hotfixescape hatch). - Multi-repo tasks — one change across several repos, PRs that land coherently.
- Run & observe — bring the stack up with healthchecks; see what's real instead of guessing.
- Phone control — approve specs, answer decisions, and merge PRs from Ground Control.
- Agent-driven development — skills, guardrails, and the orchestrator/subagent pattern.
Understand it¶
Concepts — the object model (WorkItem, Spec, Plan, Task, worktrees), the lifecycle, and the three gates, with diagrams.
Reference¶
- CLI reference — every
mshipcommand. - Configuration — the
mothership.yamlreference.
Advanced¶
- Remote access — serve over Tailscale, self-hosted relay, remote run hosts.
- Cloud workers — the unattended cloud runner runbook and its auth models.