benchturn
Past sessions count too

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.
Sign in with GitHub Read the docs

Records sessions from the coding agents you already use

  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
  • GitHub Copilot CLI
  • Cline
  • Pi
  • OpenCode
How a session travels

From your terminal to a lab, with a stop at every station.

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. You already make those. There are no tasks to pick up and nothing to annotate.

recording
Your coding agent

Claude Code, Codex, Cursor and others, inside a git repository. Keep working as usual.

working as usual
benchturn, on this machine

Records the repo tree before and after each prompt, plus the transcript. A secret scan runs before anything uploads.

uploads in background
Pending review

A real project, real code changed, a task that can be checked.

judging
Not a fit

Deleted. Nothing else happens to it.

Environment built

Rebuilt as a reproducible task at the exact commit.

reproducible
Listed, then licensed

Offered to labs. A lab receives the public repo, prompts and transcript, never your name.

offered to labs
Your payout

A share of the sale, paid on the 1st of each month via PayPal, Wise or a GitHub sponsorship.

share of every sale
Setup

One command. About a minute.

The script downloads one self-contained binary and runs benchturn init, which signs you in and connects every coding agent it finds.

  1. Sign in with GitHubYour sessions and earnings live on an account tied to your GitHub login.
  2. Agents connect themselvesCodex asks you to approve hooks once with /hooks; Cline has a Hooks switch in Settings. benchturn tells you when.
  3. Past sessions, if you wantIt looks for earlier sessions on public repos and asks before uploading any of them.
What gets recorded

Exactly enough to replay the work. Nothing you'd mind.

Recorded, per prompt

  • The repository's tree before the 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

Work outside a git repository is not recorded.

Never recorded or shared

  • Keys, tokens, passwords and .env files. A secret scan runs on your machine before upload and again at ingest; a capture that trips it is dropped.
  • Your name. Labs get no account information.
  • Anything in a repo with a .gen-ignore file. benchturn ignore writes one for you.
  • Private repos can be recorded for you, but only public ones become environments.
Where a session goes

Five stations, and an email at each one.

Every session shows up on your account with its state. We email you when it changes. We don't promise a date.

01Received

Uploaded and on your portal.

02Pending review

Can it become an environment?

03Environment built

Rebuilt as a reproducible task.

04Listed

Offered to labs.

05Licensed

A lab bought it. Your share is added to your pending payout.

A session that is not a fit is deleted. Payouts go out on the 1st of each month and cover everything owed by the 25th of the month before. Invited contributors also get a $20 welcome payment once their first three sessions are in.

Commands

Small CLI, no surprises.

Running benchturn with no arguments signs you in if needed, connects any new agent and shows your status.

benchturn statusWhat was captured, what is queued, what failed, and recent activity.
benchturn pastHave your own agent find and offer your past sessions.
benchturn accountOpen your portal: sessions, earnings, where to get paid.
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.
Questions

Good questions, short answers.

Does it slow my agent down?

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

Do sessions from before I installed count?

Yes. benchturn past has your own agent read the sessions already on disk, pick the ones on public repositories with real work in them, check each for private material and show you the list. Nothing is uploaded until you say yes to each one. The instructions it follows are public at benchturn.com/agents.md.

What makes a session a good fit?

A real project that others use or could use, with tests or a 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 or pointed it at the real cause.

How do I get paid?

Choose PayPal or Wise on your portal, or have us sponsor a GitHub account instead, such as your own project. PayPal and Wise need your legal name and country, which we keep for payment records and never show anyone.

Which systems are supported?

macOS or Linux, with git.

All aboard. Keep coding.

Install once and your sessions upload on their own.

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