benchturn
macOS + Linuxabout a minute to set up

We pay open-source engineers for the work they already do.

Your traces become RL environments in real time. You get a share of every sale.

Install the CLI Read the docs
curl -fsSL https://benchturn.com/install.sh | sh

Keys and .env files are never recorded. Any repo with a .gen-ignore file is skipped.

macOS or Linux. Takes about a minute. Read the script.

Records the coding agents you already use

Claude Code
Codex
Cursor
Gemini CLI
Copilot CLI
Cline
OpenCode
Pi
How it works

Keep working. That's the whole job.

No tasks to pick up and nothing to annotate. Labs train coding agents on real repositories at real commits, and the best source of those is work that already happened.

01

Install once

One command signs you in with GitHub and connects every coding agent it finds on the machine.

02

Work as usual

Each prompt inside a git repo is captured with the tree before and after. Uploads run in the background; your agent never slows down.

03

Get a share

Good sessions on public repos become environments. When a lab licenses one, your share is added to your next payout.

Privacy

What's captured, and what never leaves.

A secret scan runs on your machine before upload and again at ingest. A capture that trips it is dropped, not uploaded.

Recorded

  • Repository tree before and afterSo the change can be replayed exactly.
  • The transcript of each turnYour prompt, the agent's messages, the tools it called.
  • Model name and timestampPlus the full transcript at the end of a session.

Never recorded or shared

  • Keys, tokens, passwords, .env files
  • Your nameA lab gets the public repo, prompts and transcript, nothing about your account.
  • Anything in an excluded repoWork outside git, or under a .gen-ignore, stays on your machine.
Review

Every session is reviewed.

We judge whether it can become an environment: a real project, real code changed, a task that can be checked. Only sessions on public repositories qualify.

  1. Received

    Uploaded and on your portal.

  2. Pending review

    Checked for real work on a real project.

  3. Environment built

    Rebuilt as a reproducible task.

  4. Listed

    Offered to labs.

  5. Licensed

    A lab bought it. Your share goes to your pending payout.

// a session that isn't a fit is deleted. we email you when a state changes.
Payouts

Paid on the 1st, every month.

Payouts cover everything owed by the 25th of the month before. Everything you're owed shows on your portal, with the next payout date.

PAYPAL / WISE

Straight to you

Pick one on the portal. Your legal name and country are kept for payment records and never shown to anyone.

GITHUB SPONSORS

Or to a project

Have us sponsor a GitHub account instead, such as your own project.

PAST SESSIONS

Old work counts

benchturn past has your agent find qualifying sessions already on disk. Nothing uploads until you say yes to each.

CLI

A handful of commands.

Run benchturn with no arguments to sign in if needed, connect any new agent, and see your status.

benchturn statusWhat was captured, what is queued, what failed.
benchturn accountOpen your portal: sessions and earnings.
benchturn pastHave your agent find and offer past sessions.
benchturn ignoreNever record this repository.
benchturn pause / resumeStop recording for a while, then start again.
benchturn delete <id>Delete one capture here and tell us to forget it.
benchturn uninstallRemove the hooks from every agent.
FAQ

Questions.

The full answers live in the docs.

What makes a session worth something?

A real project (a library, app or tool people use, with tests or some way to check a change) and real work on it: a bug fixed, a feature added, a refactor carried through. Best of all, you steered: corrected the agent, rejected its approach, or knew something it didn't.

Can private repositories be recorded?

They can be recorded for you, but only sessions on public repositories become environments.

Does it slow my agent down?

No. Uploads run in the background on a timer and nothing waits on them.

Where does my data live?

Captures live on your machine until they are uploaded, and a copy stays there afterwards. benchturn delete removes one from both places; benchturn uninstall leaves your agents' own files exactly as they were.

Any setup steps per agent?

Two need one manual step, which benchturn init prints: Codex asks you to approve the hooks once with /hooks, and Cline has a Hooks switch under Settings → Features.

Your next session could become an environment.

One command. About a minute. Then back to work.

Sign in