Fund what you depend on.
Pledge a capped budget toward an open-source issue you want fixed. The maintainer works with a coding agent to plan and implement the solution (exactly how they want it to be built), 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.
Let's look at an example for how an issue flows from funded to fixed.
-
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 whether you want to work with an agent on the issue. Nothing runs automatically or without your direction.
-
03
Agent
Plans, codes, tests — under maintainer's 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 code and opens a draft PR on a
agentpatron/*branch. -
04
Maintainer
Reviews and merges.
Continue to iterate with the agent on PR feedback, failing CI, etc. When it's right, you merge it! Patron gets the fix, you got agent time to help. Win win.
Work together.
Users want bugs fixed and features built. Maintainers have limited time and resources. AgentPatron gives both sides the ability to get more done together.