Why riders.

AgentRiders is three things: a public, verifiable track record of real agent runs, a field manual for running agents well, and a community of the people who do it. This page is why it exists.

An agent can do a week of work in an afternoon. It can also spend $400 in tokens doing the wrong thing, confidently. Both are true at once, and that is what makes it a dragon: powerful, willful, and full of its own ideas about what you meant.

The dragons improve every quarter without your help. What does not improve on its own is the riding: the scoping, the budgets, the judgment about when to hold on and when to let go. The human is the bottleneck. That also makes the human the hero: the riding is where all the leverage is.

Autonomy is earned, not granted. Every agent gets a scope, a budget and a kill switch before its first flight, and looser reins only after it lands a few. Nobody here hands a hatchling the production keys and calls it trust.

Logs beat opinions. Opinions about agents are cheap and mostly wrong; a record of what ran, what it cost and what burned is neither. We keep the numbers in because that is the only way anyone learns anything.

The Guild exists so nobody has to learn every lesson alone, at their own expense. Somebody here has already been burned the way you are about to be. Read their log. Then fly, and log yours.

Who runs it

Max Faingezicht is the founder of AgentRiders, which is operated by Permanent Ventures Inc. He builds the site by running agents on real work and logging the flights: the log of the flight that shipped the site is public, and so is his rider profile. Find him on GitHub, or write to [email protected].

How this site is made

The chapters and lessons are written by the founder. Agents are used to build the site and to draft; every number in a flight log comes from the rider who flew it.

Where the corpus comes from

The Flight Log corpus, public pull requests authored by coding agents, is built from public GitHub activity: the AIDev dataset (AIDev: Studying AI Coding Agents on GitHub, Li et al., CC BY 4.0) for the backfill, GH Archive for new flights, and the GitHub API for enrichment. Pages show metadata, computed numbers and short verbatim excerpts with links, never diffs or full PR bodies, which stay under their repositories' own licenses on GitHub. Each flight names the agent and its maker and credits the author by the name on their public GitHub profile, with an author page per account once a flight is on the record. Authors can opt out at any time, which also deletes the stored profile fields; the pages are not affiliated with GitHub or with any repository or agent maker.