New 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.

Records the coding agents you already use

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

Keep working. benchturn handles the rest.

There are no tasks to pick up and nothing to annotate. Install once, and every session on an open-source repository can become an environment a lab licenses.

01Install and sign in

One command downloads a single binary, signs you in with GitHub and connects every coding agent it finds on the machine.

02Work as usual

Each prompt records the repository before and after, plus the transcript. Uploads run in the background on a timer; your agent never slows down.

03Get paid when it sells

Every session is reviewed. When a lab licenses one, you get a share of the sale. Sessions that are not a fit are deleted.

Privacy

Precise about what is recorded, and what never is.

Only work inside a git repository is recorded. Only sessions on public repositories become environments.

What is recorded

For each prompt you send to a connected agent inside a git repository:

  • 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. At the end of a session, the full transcript.

What is never recorded or shared

Checked on your machine, then again on our side.

  • Keys, tokens, passwords and .env files. A secret scan runs before upload and at ingest; a capture that trips it is dropped.
  • Your name. A lab receives the public repository, the prompts and the transcript, with no account information attached.
  • Anything in a repository you excluded. A .gen-ignore file at its root skips it entirely; benchturn ignore writes one.
Where a session goes

Every state, visible on your account.

We email you when a state changes. We don't promise a date.

  1. Received

    Uploaded and on your portal.

  2. Pending review

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

  3. Environment built

    Rebuilt as a reproducible task.

  4. Listed

    Offered to labs.

  5. Licensed

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

A session that is not a fit is deleted.
CLI

One binary. A handful of commands.

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

benchturn init

Set up this machine. Safe to re-run; it finishes whatever isn't done.

benchturn status

What was captured, what is queued, what failed, and recent activity.

benchturn past

Have your agent find and offer your past sessions.

benchturn account

Open your portal.

benchturn ignore

Never record this repository.

benchturn pause / resume

Stop recording for a while, then start again.

benchturn delete <id>

Delete one capture here and tell us to forget it.

benchturn add-machine

A one-hour code that adds another machine to your account.

benchturn uninstall

Remove the hooks from every agent.

FAQ

Questions, answered.

What does a lab actually buy?

An environment: a real repository at a real commit, a task someone actually asked for, and a way to check the result. benchturn turns your good sessions on open-source projects into these, licenses them to labs, and pays you a share of every sale.

Do sessions from before I installed count?

Yes. Run benchturn past and your own agent (Claude Code or Codex) 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 at benchturn.com/agents.md.

Which agents need an extra step?

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

What about private repositories?

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

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 takes the hooks out of every agent's settings and leaves your own agents' files exactly as they were.

Start earning from the work you already do.

macOS or Linux, with git. Takes about a minute.

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

Read the docs · Read the script