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

We convert your traces into RL environments. You get a share of every sale.

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

Only your open-source repos are synced. Key files and .env files are never recorded. Any repo with a .benchturn-ignore file is skipped.

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

~/code/tokio

Records the coding agents you already use

Private by default

Secret files stay on your machine.

Files named like secrets, such as .env, *.pem and id_rsa, never go into a snapshot. Keep secrets out of your prompts, add a .benchturn-ignore to any repo you want left out, and we redact what we find in review. Your name is never shared with a lab.

What is never recorded →

Keep working

No tasks to pick up. Nothing to annotate.

AI labs train coding agents on real repositories at real commits, with a task someone actually asked for. The best source is work that already happened. benchturn records your sessions on open-source projects and turns the good ones into environments.

How it works →
  • The repository's tree before your prompt and after the agent stops, so the change can be replayed exactly.

  • The transcript of that turn: your prompt, the agent's messages, and the tools it called.

  • The model name and a timestamp. Uploads run in the background on a timer; your agent never slows down.

One binary

A few commands, all optional.

Running benchturn with no arguments sets up this machine if it isn't yet, and otherwise shows your status.

Every command →
benchturn commands
benchturn statusWhat was captured, what is queued, what failed.
benchturn uploadPick past sessions to upload for review.
benchturn allowWhich repos are recorded: the policy, named repos, exclusions.
benchturn offNever record this repository; on to undo.
benchturn pausePause passive income; resume to start again.
benchturn delete <id>Delete one capture here and tell us to forget it.
benchturn accountOpen your portal: sessions, earnings, payouts.

Questions

Which sessions can become environments?

Sessions on public GitHub repositories with real code changes: a bug fixed, a feature added, or a refactor carried through. Setup uploads and syncs only sessions in your open-source repos; sessions in private repositories stay on your machine.

Does it slow down my agent?

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

Do any agents need setup?

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

Can I take it back out?

benchturn delete removes a capture from your machine, and its record and repository snapshot from us; write to hello@benchturn.com to have everything removed. benchturn uninstall takes the hooks out of every agent and leaves your own agents' files exactly as they were.

Who sees my name?

No lab does. A lab receives the public repository, the prompts and the transcript, with no account information attached. Stripe collects your identity and bank details on its own pages; PayPal and Wise need your legal name and country, which we use only to pay you and for our payment records.

Get paid for the work you already do.

$ curl -fsSL https://benchturn.com/install.sh | sh