Don't just send a check.
Send an agent.
Patrons pledge agent time toward the issues they need fixed. Maintainers spend that time how they want, directing Claude Code through their codebase in their style, on their schedule. The work the community cares about gets done. The maintainer stays the artist. And the slop‑PR problem solves itself.
A register of recent commissions.
A made‑up week of patronage. In production, the ledger is the single page where patrons watch their pledges turn into upstream pull requests.
Resolver hangs on cyclic optional dependencies
TLS‑ALPN renewal under high cert churn
Cookie middleware loses Secure flag in dev
Memory regression in window functions
Email provider double‑sends on retry
How it stays clean.
AgentPatron is structured so the agent serves the maintainer. Three principles, written down so nobody has to remember them.
-
i.
The artist directs.
The agent never runs without the maintainer's permission. Plans are revised until the maintainer would build it that way themselves. Every pull request is reviewed and merged by hand. Patronage doesn't buy a shortcut around the review.
-
ii.
Patrons fund work, not access.
Pledges go toward specific issues, not generic sponsorships. If the maintainer declines an issue, the pledge is refunded. No subscriptions, no surveillance, no usage you didn't ask for.
-
iii.
One source of agent PRs you actually asked for.
Anyone can still open a drive‑by AI PR against an open source repo. That's GitHub, not us. What AgentPatron guarantees is that its agent never opens one. Every PR from AgentPatron sits behind a plan the maintainer approved, on a repo that opted in.
The work has two voices.
A patron and a maintainer enter the same commission from different ends. Three steps each. The agent is the medium between them.
Fund what your team actually depends on.
Find the issue you need fixed.
Browse a maintainer's open issues. Pick the security patch, the long‑tail bug, the missing feature your company runs into in production.
Pledge agent hours, not a subscription.
Your pledge becomes Claude Code time inside the maintainer's repo. No middleman PRs. No contractor markup. The agent works for the artist.
Receive the fix upstream.
When the maintainer merges, you get the change in the next release, same as any normal upstream contribution. No fork, no internal patch.
Take patronage on your terms.
Mark the issues you'll accept.
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.
Direct the agent.
Revise the plan until it matches how
you would build it. Then the agent codes that
plan and opens a draft PR on a protected
agentpatron/* branch.
Approve, refine, ship.
Triage failed CI and reviewer feedback automatically. You stay in the review seat. When it's right, you click merge. The fix ships.
Begin the commission.
Patron or maintainer, GitHub is the door. Tell us which voice you'd like to read first — your dashboard will open on that side, and you can switch any time.