Fund what you depend on.
Pledge a capped budget toward an open-source issue you need fixed. The maintainer picks a coding agent and directs it through their codebase, in their style — drawing from your pledge until it ships. Whatever they don't spend, you get back.
Refunded automatically if no maintainer claims your pledge in 60 days. Anything unused after a run is refunded too.
Loading live ledger…
Maintainer? See it on your repo →How a fix gets made.
One issue. One PR. Four moves between a patron, a maintainer, and the agent that works for them.
-
01
Patron
Pledges against an issue.
Pick the security patch, the long‑tail bug, the missing feature your team hits in production. Set a cap — say, $5 of agent time. Refunded automatically if no maintainer claims your pledge in 60 days. Anything unused after a run is refunded too.
-
02
Maintainer
Accepts the scope.
Decide what's open for patronage and what isn't. Reject anything that doesn't fit the project's direction. The agent never runs unprompted or off‑topic.
-
03
Agent
Plans, codes, tests — under direction.
Drafts a plan in an isolated sandbox with no git credentials. The maintainer revises it until it matches how they would build it. Then the agent writes the patch and opens a draft PR on a protected
agentpatron/*branch. -
04
Maintainer
Reviews and merges.
Hand the agent failing CI to fix, or send back reviewer feedback as a revision plan you approve. When it's right, you click merge — and the patron gets the change in the next release.
Work together.
Patron or maintainer, GitHub is the door. Tell us which side you'd like to start on — your dashboard will open there, and you can switch any time.