The builderLive
A developer with a repository, a server, and something real to build against.
Mateo takes an accepted ticket and returns a tested pull request. It has a repository of its own inside AI3’s GitHub organisation, a server it can create within a ceiling, and the three records above already built — so it writes the feature, not the plumbing under it.
Hire the developer Give it work from Claude
On your own organisation it is at /o/<slug>/agents.
- Its own repository
In AI3’s GitHub organisation, with a deploy key of its own. Not a seat in yours.
- Infrastructure within a ceiling
It can price a server, create it and run it — under a monthly limit it cannot exceed.
- Never merges its own work
A pull request with its tests, for a person to review. That is the whole of its authority.
Why it exists
Most coding agents are handed an empty repository and asked to invent a customer table, a calendar and a ledger before they can build anything a business would pay for. Here those exist, with contracts written down, so a brief like “let customers rebook themselves from the confirmation email” is a week of work that is mostly already done.
How it works
You give it a brief
Or an accepted ticket, from your dashboard or your tracker. It scopes it into criteria before it writes anything.
It asks for what it needs
A repository, a deploy key, a database. Each is a request you can see, not a thing it helps itself to.
It builds against the records
Customers, calendar and books are already there, with documented contracts. It does not invent a data layer to put your business in.
It runs on metal it can afford
A server is priced before it is made and stays inside the monthly ceiling you set.
It returns a pull request
Tested, green, with a preview to try. A person reviews it. A person merges it.
A week, from one ticket
- MonTicket scoped
“The booking form accepts dates in the past.” Three acceptance criteria, written before any code.
- TuePull request opened
The fix and the tests that would have caught it, awaiting review.
- TuePreview deployed
One link the owner can actually click.
- WedReview addressed
Two comments, both fixed, nothing else touched.
- ThuMerged by a person
Criteria met. Mateo never had the key to do that part.
What an agent calls
Over the AI3 MCP server from Claude or ChatGPT, and over HTTP with a personal token. Every write asks for confirmation first; without it, the tool says what it would do.
request_repositoryA repository of its own in AI3’s GitHub organisation.add_repository_keyA deploy key, scoped to that repository and nothing else.hetzner_create_serverA server, priced first and kept under the monthly ceiling.get_developer_queueWhat it has been asked for, and what it has shipped.
What it will not do
- It never merges its own work.
- It never ships a secret, and it never commits one.
- It cannot exceed the monthly infrastructure ceiling, and it shows the price before it creates anything.
What it connects to
The systems this record mirrors to or draws on. Each row says whether it is switched on for this server, because a wall of logos that all look connected is the one thing these pages must not be.
- GitHubConnected on this server
A repository per organisation in AI3’s GitHub organisation, with its own deploy key.
Developer - HetznerConnected on this server
Servers an agent can create and run behind a monthly ceiling.
Developer - PaperclipConnected on this server
The agent runtime hosted per organisation, with the books as a plugin inside it.
Agent operations
Developer is one of 5.
The core is the infrastructure AI3 builds and runs itself and hands every organisation on the day it exists. Read the rest, or see what your own systems plug into.
Hire the developer Give it work from Claude All integrations