Overview
maintainer-agent is an unattended maintainer for one repository. It runs on a timer, reviews what arrived, files what it found, and prunes what merged. It can merge, but only against a receipt that somebody watched a guard go red. It maintains lacs-project/sysknife and this repository, on one laptop, in the owner's name.
The design is built around three questions. To stop damage, a deny wall of 37 verbs is generated per profile and spelled from every directory each tool could be installed in, passed to the model runner as settings that outrank its own permission mode. The wall covers git push, gh pr merge, cargo publish, gh release, credential files, and the key that signs its own verification receipts.
To stop inventing, every number it publishes is recounted with a command, every path resolves against the tree, and every guard is mutated before it is called a guard. A run that found nothing posts nothing. The transcript records what it ran, not what it said, and maintainer audit compares the two.
To stop merging broken code, a green board is not proof. A merge needs an observed receipt: the gate runs the test in a container, applies a mutation, runs it again, and records a receipt only if it passed clean and failed mutated. An unattended run cannot write any other kind. It is not a boundary against a kernel exploit, and containment.md says so in the same words. It is not a general safety mode.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Maintainers use maintainer-agent to run an unattended maintainer for one repository on a timer, reviewing what arrived, filing what it found, and pruning what merged.
- Maintainers use maintainer-agent to maintain lacs-project/sysknife and this repository on one laptop in the owner's name.
- Maintainers use maintainer-agent to block dangerous verbs such as git push, gh pr merge, cargo publish, gh release, credential files, and the key that signs its own verification receipts.
- Maintainers use maintainer-agent to recount every published number with a command, resolve every path against the tree, and mutate every guard before it is called a guard.
- Maintainers use maintainer-agent to record a transcript of what it ran, not what it said, and compare the two with maintainer audit.
- Maintainers use maintainer-agent to require an observed receipt for a merge: the gate runs the test in a container, applies a mutation, runs it again, and records a receipt only if it passed clean and failed mutated.
- Maintainers use maintainer-agent to deploy it four ways in order of how much they have to trust the machine.
- Maintainers use maintainer-agent to study fifty-one defects that reached a working system, each with the measurement that found it.
Features
AI assistant
Natural language interface
Workflow automation
Reviews
No reviews yet. Be the first to share your experience!
FAQ
What stops it doing damage?
A deny wall of 37 verbs, generated per profile and spelled from every directory each tool could be installed in, passed to the model runner as settings that outrank its own permission mode. It blocks git push, gh pr merge, cargo publish, gh release, credential files, and the key that signs its own verification receipts.
What stops it inventing things?
Every number it publishes is recounted with a command, every path resolves against the tree, and every guard is mutated before it is called a guard. A run that found nothing posts nothing. The transcript records what it ran, not what it said, and maintainer audit compares the two.
What stops it merging something broken?
A green board is not proof. A merge needs an observed receipt: the gate runs the test in a container, applies a mutation, runs it again, and records a receipt only if it passed clean and failed mutated. An unattended run cannot write any other kind.