Maintainer Autopilot CLI
Maintainer Autopilot runs AI code changes as a resumable pipeline with a single-writer lock and checks before merge.
- 99 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The pipeline runs an agent with write access to the workspace and can push branches and PRs to GitHub.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/maintainer-autopilotDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The pipeline runs an agent with write access to the workspace and can push branches and PRs to GitHub.
This is third-party code. Review the repository files before installing.
What it does
A local CLI turns a maintenance task into a stateful pipeline: implementation, review, finalization, ready to promote, open PR and CI. The core rule is one task, one lineage, one active writer. An atomic lock keeps two runs from writing the same workspace. State lives in `.maintainer-autopilot/state.json`. Implementation runs through `codex exec --sandbox workspace-write`, review runs read-only, and configured shell gates run in order and stop on the first failure. After a failure the task moves to `REPAIR_REQUIRED` and the next promotion updates the same PR. Auto-merge is off by default.
Who it is for. Independent developers and maintainers who push changes through AI coders and want them verified before merge.
Good fit when
- AI changes must be tracked per task so work resumes after a CI failure.
- Two agents must not change one repository at the same time.
- A PR needs a read-only review and a set of mandatory gates first.
- The workflow must survive a change of coding agent.
Not a fit when
- You need a ready cloud service rather than a local tool.
- You need seamless handoff between different agents, which version 0.1 lacks.
- The project has no Node.js 22 and no Git.
Example request
Run one local task through maintainer-autopilot and show the state and gate results before promotion.Limitations
Version 0.1 is labeled a public beta: run it on a branch, review every change and keep auto-merge off. Codex is the default agent, another CLI is configured by hand, and automatic quota detection and handoff from Codex to another agent are roadmap items. It needs Node.js 22 and Git, and optionally `gh` for promotion. Gates are configured by hand; the pipeline only runs them in order.
How to disable. Remove the package with `npm uninstall -g maintainer-autopilot` and the `.maintainer-autopilot` folder in the project. Close open PRs and branches by hand.
FAQ
What happens when a gate fails?
The task enters `REPAIR_REQUIRED`, the attempt counter grows and no new task starts. The next promotion updates the recorded PR.
Which AI agent does it use?
Codex CLI by default, with a `workspace-write` sandbox for edits and read-only mode for review. The command and arguments can be replaced.
Is auto-merge on?
No, it is off by default. Promotion to GitHub is a separate step after review and gates.
What does `state.json` hold?
Task status, attempt history, candidate receipts and gate output. The file lives in `.maintainer-autopilot/`.
What is a candidate receipt?
A record with the commit SHA and SHA-256 hashes of changed files that the pipeline writes at promotion.
Discussion
No questions or reviews yet.
Related
CLI toolsGitHub Actions workflows run on your machine, and a failing step pauses so the agent can fix the file and retry it.
A background daemon loops over GitHub or Forgejo issues, drafts specs, reviews and fixes PRs until they are ready for human merge.
A pattern library and skill set for recurring agent loops: issue triage, dependency cleanup, PR babysitting
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
A Rust CLI and TUI: agents in containers, parallel tabs, TOML workflows from issue to PR and a scheduled agent squad
release-it combines version changes, Git tags and package publishing in a configurable release workflow with a preview mode.
README in short
The README asks who makes AI-written code safe to merge, describes the audience, the state graph and safety properties. Requirements, a quick start with an npm install and a sample config follow.