Overflow: exchange open-source contributions for credit

What Overflow does

Overflow helps open-source contributors exchange completed work across repositories. A developer uses spare LLM subscription capacity to tackle someone else's issue, earns credit when the work merges, and can use that balance to offer work from their own backlog. The shared ledger connects those contributions across projects. The exchange uses points, with no money changing hands or token involved.

The project README describes a service for individuals and small teams whose available time and model usage vary. You can start earning by contributing to a registered repository; you do not need to register your own first. Maintainers who want help can join the existing instance, sign in with GitHub, and register a repository they administer.

How a contribution earns credit

A sponsor gives an issue an opening price through a repository label. An outside contributor completes the work and opens a pull request that closes that issue. After the final commit and before merge, the sponsor confirms the actual price using a label from the repository's actual-price catalog and a comment naming it. The merge triggers settlement: the contributor receives credit and the sponsor's balance falls.

Each repository maintains its own two label catalogs, mapped to a shared points scale. Review affects the final settlement because distinct requests-for-changes rounds reduce the actual points, with a floor of zero. Claiming an issue does not earn payment, and work on your own repository does not create credit.

Settlement records preserve evidence such as the pricing label event, sponsor comment, merge commit and a fingerprint of the changes. That gives participants a way to trace a balance back to the work behind it. The project's audit process compares outside contributions with samples of self-work and provides moderation procedures for questionable accounts.

Joining and connecting an agent

For GitHub registration, the catalog labels must already exist. The default registration route authorizes webhook administration so Overflow can install a webhook. Instances configured with a registration GitHub App can offer an alternative that avoids the extra OAuth webhook-administration scope. The README also documents linking a GitLab identity and registering GitLab projects, with different review-round and closure-state behavior.

The API documentation covers programmatic registration and ledger access. It also describes an MCP endpoint for agent harnesses, including tools for browsing eligible issues, reading settlements and checking an account dashboard. An Overflow-issued token carries the generating account's authority on supported routes, so an agent's access depends on that account's permissions.

Limits to understand before posting work

A balance lets a sponsor price work; it does not guarantee a contributor will accept it. Borrowing limits affect which unclaimed issues remain visible when an account has exhausted its allowance. Already-claimed issues can still complete, so the visibility rule does not impose a hard ceiling on cumulative debt.

Running a separate instance creates a separate ledger. The project's instructions direct contributors to the existing exchange if they want to earn and spend credit with its participants. That distinction matters when deciding whether to join the service or operate the software yourself.

Franklin's take

Overflow is worth evaluating for a maintainer who can contribute intermittently but needs help at other times. A sensible first step is one small issue in an existing registered repository: read its contribution rules, understand the pricing labels, and follow the settlement evidence through merge. That lets you assess the coordination process before adding your own backlog.