benchturn

// for people who ship open source with coding agents

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.

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.
~/src — sh

      

01what this is

AI labs train and test coding agents on environments: a real repository at a real commit, a task someone actually asked for, and a way to check the result. The best source of those is work that already happened.

benchturn records your coding-agent sessions on open-source projects, turns the good ones into environments, licenses them to labs, and pays you a share of every sale. There are no tasks to pick up and nothing to annotate.

02how it works

  1. 1Run the install script. It downloads one self-contained binary and runs benchturn init, which signs you in with GitHub and connects every coding agent it finds.
  2. 2Keep working. For each prompt inside a git repository, benchturn records the tree before and after and the transcript of that turn. Uploads run in the background on a timer; your agent never slows down.
  3. 3We review each session. A good one is rebuilt as a reproducible task and offered to labs. One that is not a fit is deleted.
  4. 4When a lab licenses it, your share is added to your pending payout. Payouts go out on the 1st of each month.

03what leaves your machine

recorded
  • The repository's tree before the prompt and after the agent stops
  • The transcript of that turn: your prompt, the agent's messages, the tools it called
  • The model name and a timestamp
  • The full transcript, at the end of a session
never recorded or shared
  • Keys, tokens, passwords and .env files. A secret scan runs before upload and again at ingest.
  • Your name. A lab gets the public repo, prompts and transcript, nothing else.
  • Anything in a repository with a .gen-ignore file
  • Work outside a git repository

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

04supported agents

  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
  • GitHub Copilot CLI
  • Cline
  • Pi
  • OpenCode

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.

05past sessions

Sessions from before you installed count too. Run benchturn past and your own agent reads the sessions already on disk, picks the ones on public repositories with real work in them, checks each for private material, and shows you the list. Nothing is uploaded until you say yes to each one.

The instructions it follows are public: benchturn.com/agents.md.

06where a session goes

statemeaning
receivedUploaded and on your portal.
pending reviewWe judge whether it can become an environment: a real project, real code changed, a task that can be checked.
environment builtRebuilt as a reproducible task.
listedOffered to labs.
licensedA lab bought it. Your share is added to your pending payout.

A session that is not a fit is deleted. We email you when a state changes. We don't promise a date.

07getting paid

shareA share of the sale, for each session a lab licenses.
whenThe 1st of each month, covering everything owed by the 25th of the month before.
howPayPal or Wise, or we sponsor a GitHub account instead, such as your own project.
welcomeInvited contributors get $20 once their first three sessions are in.

08commands

commandwhat it does
benchturn initSet up this machine. Safe to re-run.
benchturn statusWhat was captured, queued, failed.
benchturn accountOpen your portal.
benchturn pastHave your agent find and offer past sessions.
benchturn ignoreNever record this repository.
benchturn pauseStop recording for a while. resume starts again.
benchturn delete <id>Delete one capture here and tell us to forget it.
benchturn uninstallRemove the hooks from every agent.

All commands in the docs

09questions

Do I have to change how I work?
No. Keep using your coding agents as usual; sessions upload on their own.
What if a repository is private or a client's?
Run benchturn ignore in it, or add a .gen-ignore file. Nothing in it leaves your machine. Only public repositories become environments.
Can I take something back?
benchturn delete <id> removes a capture from your machine and tells us to forget it.
When will I hear back?
We email you when a session changes state. We don't promise a date.

Install once. Get paid for the work you were going to do anyway.

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