Hand a coding task to a developer for a fixed price.
A failing test, a migration, an auth flow you did not set out to learn. The alternative is your own time and an unknown number of tokens. Name the price, hand it off, and read what comes back on a branch of its own. You are charged only if you accept it.
The developers who pick these up are invited by name — a small group, no open sign-up, no bidding.
The reason you can say yes to a stranger.
Handing work to a stranger comes down to what they can see — and that is yours to set, posting by posting. Whatever passes through us is checked on the way out. Everything is checked on the way back.
- ▹You choose the scope — the issue alone, one slice of files, or the whole repository — set by the posting, not by them.
- ▹Secrets scanned first — on a scoped posting whatever passes through us is checked, and a known credential pattern stops the hand-off. choose the whole repository and nothing passes through us, so there is no scan — you are shown exactly that before you post.
- ▹No push access — the patch returns through us, onto a branch of its own.
From a sentence to a branch.
Three steps, and two of them are decisions only you can make. Everything between them runs without you.
You are stuck on something small.
- 01Say what is wrong, where you already areOne URL into Claude Code, Codex or any MCP client, then describe the problem in a sentence. It hands back a link: you sign in, connect the repo, and save a card — saving one is not a charge. Some repos take another pass to get through.
- 02A developer picks it upThey see what you chose to share, and no way to push to it. On a scoped posting, whatever passes through us is checked for known credential patterns before it leaves; hand over the whole repository and it goes to them directly, unscanned.
- 03You read the change and decideIt comes back on a branch of its own. A patch that touches your CI, your git internals or an install script is refused; a new dependency applies unless you turn that off. On a priced posting, accept and the developer is paid (from your card, or from platform credit if you hold any). A free posting has no charge. Reject and nothing moves.
Early, and honest about it.
Handing off a task, scoping what a developer can see, matching it, and returning a checked change on its own branch all work now. The developers taking this work are a small group we know by name rather than an open pool.
364 live roles + contributions across 9 sources · refreshed every 5 min
Name it. Price it. Read what comes back.
Describe the task in the agent you already use and hand it off. Everything up to accepting the change runs today.