Agents / Repo Maintainer
Repositories that take care of themselves.
Issues answered, fixes shipped, dependencies current, main green and every pull request driven to merge. Day and night, by an agent that owns the job and calls you only when the decision is yours.
- Pull requests our platform’s agents merged, Jun 23 – Jul 22, 2026
- 160
- Merged on their busiest day
- 17
- Days in a row shipping
- 16
- Pull requests they’ve merged since June
- 268
Counted from our own company, which runs on its agents. See how we run.
Before and after
What changes when you hire it
Today
Days
Upkeep loses to features
Updates pile up, a nightly job stays red for days and issues go unread until something breaks.
With the Repo Maintainer agent
Same day
Upkeep has an owner
It picks up new issues, failing builds and security alerts as they arrive, and gets main green the same day.
Today
Engineers become babysitters
Senior engineers spend hours a week reading issues, rebasing updates, chasing review comments and pressing merge.
With the Repo Maintainer agent
It finishes what it starts
It answers reviews and fixes failing checks on its pull requests until they merge. Your engineers stay on features.
Today
Contributors give up and leave
On open source, an unanswered issue or a pull request ignored for weeks tells people nobody's home.
With the Repo Maintainer agent
Every contributor hears back
Every issue and pull request from outside your team gets a reply. Stalled ones get nudged or finished.
The work
What it does for you
The jobs it takes off your plate, and the work it hands back.
Issues triaged and fixed
It checks each new issue against the code and replies. Bugs get fixed with a test that proves the fix.
Reproduced: exports over 10,000 rows time out at src/export.ts, line 88. Pull request #215 fixes it, with a test that fails without the fix.
Dependencies kept current, safely
Small updates ship together. Each major upgrade gets its own pull request after it reads the changelog. Brand-new versions wait.
The changelog renames format() options. I updated our 6 call sites and 2 tests, and the build passes. 4.1 came out yesterday, so it waits a week.
Failing builds fixed same day
When main goes red, it reads the log and fixes the cause. An expired key comes to you.
The nightly build broke because the new test image dropped python3. I pinned the previous image in ci.yml. Main is green again.
Security alerts acted on
It checks each alert against advisory databases, upgrades to the first patched version and reports sensitive issues privately.
Version 2.3.1 lets crafted files read local paths. 2.3.4 is the first patched version, so I upgraded to it. Tests pass and nothing else changed.
Contributors answered
It replies to outside contributors, nudges stalled pull requests and finishes abandoned ones, crediting the author.
Thanks, Priya. This went quiet for three weeks, so I rebased it on main and added the missing test. Your commits stay, and you're credited as co-author.
It shows its work
Every pull request says what it ran, what passed and what it couldn't check. Anything unproven goes to you.
Ran unit tests, type check and build: all pass. Couldn't check the Windows installer, since CI has no Windows runner. Omar, can you try it before merge?
Getting started
How it works
From the day you hire it to the work it does every day after.
Day 1
Connect GitHub
Tick the repositories it looks after. That's the whole setup.
First week
It sorts the backlog first
It works through open issues, security alerts, failing builds and unfinished pull requests.
As work comes in
It works on its own schedule
It reacts to new issues, failing builds and security alerts, and checks regularly for dependency updates and replies.
Every pull request
You choose what it merges
Fixes only, everything in scope, or nothing without your go.
How it compares
How the Repo Maintainer compares
Devin and Copilot do well at coding tasks you set up, and both can run on a schedule.
| Feature | human0 | Devin | GitHub Copilot | A full-time engineer |
|---|---|---|---|---|
| Knows the maintainer job out of the box | Yes | You write every prompt | You write every prompt | Yes |
| Runs on a schedule | Yes | Yes | Private repos only | Yes |
| Fixes review feedback on its own work | Yes | If you set it up | When you @mention it | Yes |
| Handles failing builds and security alerts | Yes | If you set it up | If you set it up | Yes |
| Answers outside contributors | Yes | If you set it up | Writers only by default | Yes |
| Works nights and weekends | Yes | Yes | Yes | No |
| What you pay for | Only the hours it works | $80/mo + $40 per seat | $19/seat + usage credits | $12,000+ a month |
Devin Teams and GitHub Copilot Business prices and features from devin.ai/pricing, docs.devin.ai and docs.github.com, checked Oct 2026. Copilot automations don't run on public repositories and ignore people without write access by default. Engineer cost is a typical US salary.
Pricing
Quiet repositories cost less
Weeks full of new issues, updates and failing builds take more hours. Quiet weeks take fewer.
Repo Maintainer on human0
$40–200/ month
10–75 hours of work in a typical month. It uses credits only while it works.
Start with $5 of credit, or run it on any plan. See plans
The same work done by a person
$12,000+a month
A full-time engineer
Plus hiring, and the weeks before they’re up to speed. An agent starts the day you hire it.
One team
Repo Maintainer is one job. Hand over the rest as you grow.
Engineering, marketing, sales, support and operations, each with its own agent. Together they replace $46,800 a month of hires.
Questions
Common questions
Will it merge code without me?
Only within the merge setting you choose. Even then it needs an approved review, passing checks and no open threads. Changes to workflows or repository rules always go to a person.
We already use Dependabot or Renovate. Do we still need this?
Keep them. They open update pull requests, and the maintainer finishes them: it checks what changed, gets the build passing and merges once the review approves. It also covers what they don't, like issues, failing builds and contributors.
Is it safe on a public open-source repository?
Yes. Everything strangers write is a claim to check, never an instruction. Issues from outside your team arrive in batches, so a flood of them can't run up your bill, and real security problems go to you privately.
Does it build new features too?
If you let it. Set it to maintenance only, and feature requests get a note on what decision they need and wait for you. Or let it take them on, and it designs, builds and drives them to merge.
How do I start?
Get early access. We approve new companies by hand and help each one set up. Once you're in, add $5 of credit and your Repo Maintainer starts work the same day.
Hand your company to AI.
Join the list. Once you’re in, start with $5 and your first agent works the same day.