Learn to build agents. Free, in order.
Everything here is public and needs no account. Members get the same material plus tutorials for the team tools and a Q&A agent in the builders portal.
Full-stack developer, 0 → 1
five stages, each with a projectTerminal & git
Shell basics, branches, pull requests, rebase vs merge. Project: your first PR to a sandbox repo.
Python fundamentals
Types, packaging with poetry or uv, pytest. Project: a CLI that reads JSON and prints a table.
HTTP & APIs
REST, FastAPI, auth, JSON schema. Project: a small API with two routes and tests.
Frontend basics
HTML/CSS, React, a static Next.js page. Project: a page that renders your API's JSON.
Ship it
Railway, Vercel, DNS, CI. Project: your API and page live on a subdomain.
Building an agent, 0 → 1
the short course behind every member repoMCP in 20 minutes
Tools, resources, prompts. stdio vs Streamable HTTP. Why a stateless proxy works.
A tool is a typed function
Models pick tools by name and description. Where to spend the effort and where not to.
Scaffold and run locally
One command to a working server; connect it to Claude on your laptop and call it.
Calling an LLM from your agent
Model and key from the environment, never the repo. Treat input as data, say so in the prompt.
Tests a model would write
One test per tool, called the way a model calls it. This is what the gate runs.
Ship behind one endpoint
Register, host, and call your tool through the fleet gateway from any MCP client.
Core concepts
the ideas the platform is built onCOPY then REFERENCE
The scaffold is copied once into your repo. The rules are referenced live by version. That is how a fleet of independent repos moves together.
The gate decides, the AI advises
Deterministic checks are the only thing that can block a merge. Model output is a comment you can ignore.
The manifest is the seam
One YAML file at the repo root that every tool reads: the gate, the deployer, the gateway, the review agent.
GitHub is the database
Roster, hosting, quota and history are git commits and comment markers. Nothing to back up, nothing to drift.
Secrets never cross accounts
Your CI sends public metadata. The platform acts with its own keys on its own side. Fork PRs see nothing.
Every authorization is a PR
Joining, hosting, quota changes: a YAML diff a human merges, visible forever.
Watch and read
recordings and long-formWeekly build call recordings
Every Monday after the bot runs. Demos of what shipped, live debugging of member PRs.
RFC 001 · migration and deploy
How adoption, registration and hosting were designed, with the alternatives that were rejected.
Design Q&A
Every settled decision and its reasoning, in one page. Read this before proposing a change.