The tree before and after
For each prompt inside a git repository: the repository's tree before the prompt and after the agent stops, so the change can be replayed exactly.
New Sessions from before you installed 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-ignorefile 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
- Pi
- OpenCode
How it works
One command. Then keep working the way you do now.
No tasks to pick up and nothing to annotate. 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.
- 01
Install and sign in with GitHub
One self-contained binary.
benchturn initconnects every coding agent it finds. - 02
Work as usual
Uploads run in the background on a timer. Your agent never slows down.
- 03
Get paid when a lab licenses it
Every session is reviewed. Licensed ones pay you a share of the sale.
What gets recorded
Exactly enough to replay the work. Nothing private.
The transcript of each turn
Your prompt, the agent's messages, the tools it called, the model name and a timestamp. The full transcript at the end of the session.
Secrets never leave
Keys, tokens, passwords and .env files are never recorded. A secret scan runs on your machine before upload and again at ingest. A capture that trips it is dropped.
Your name is never shared
A lab receives the public repository, the prompts and the transcript, with no account information attached.
Skip any repository
benchturn ignore writes a .gen-ignore and keeps it out of git. Work outside a git repository is not recorded at all.
Past sessions count
benchturn past has your own agent find qualifying sessions already on disk. Nothing uploads until you say yes to each one.
The CLI
Small surface. Every command is safe to re-run.
Running benchturn with no arguments signs you in if needed, connects any new agent, and shows your status.
# install the binary into ~/.local/share/benchturn curl -fsSL https://benchturn.com/install.sh | sh # set up this machine; finishes whatever isn't done benchturn init # Codex: approve the hooks once /hooks # Cline: Settings → Features → Hooks
# your own agent (Claude Code or Codex) reads the # sessions on disk and shows you the ones that qualify benchturn past # the instructions it follows are public # https://benchturn.com/agents.md # nothing uploads until you say yes to each one
# never record this repository benchturn ignore # stop recording for a while, then start again benchturn pause benchturn resume # delete one capture here and tell us to forget it benchturn delete <id> # remove the hooks from every agent benchturn uninstall
# captured, queued, failed, recent activity benchturn status # open your portal: sessions and earnings benchturn account # a one-hour code that adds another machine benchturn add-machine benchturn update
Where a session goes
Every upload is reviewed. You see each state on your portal.
- 01
Received
Uploaded and on your portal.
- 02
Pending review
A real project, real code changed, a task that can be checked.
- 03
Environment built
Rebuilt as a reproducible task.
- 04
Listed
Offered to labs.
- 05
Licensed
A 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.
Getting paid
A share of every sale. Paid monthly.
Payouts
Everything you are owed shows on your portal, with the next payout date.
- Schedule1st of each month
- CoversEverything owed by the 25th before
- MethodsPayPal, Wise, or GitHub Sponsors
- Invited contributors$20 after your first three sessions
The instructions are public
When your agent looks through past sessions, it follows a plain markdown file anyone can read. It never edits your session files, and nothing leaves your machine until you have seen the list and said yes.
# agents.md
benchturn scan --json
# judge: real project, real work,
# the person steered
# redact, then ask before upload
What does a lab actually get?
An environment: a real repository at a real commit, a task someone actually asked for, and a way to check the result. A lab receives the public repository, the prompts and the transcript, with no account information attached.
Do private repositories count?
Private repositories can be recorded for you, but only sessions on public repositories become environments.
What makes a session a good fit?
A real project (a library, application or tool other people use, with tests) and real work on it: a bug fixed, a feature added, or a refactor carried through. Best of all, you steered: corrected the agent, rejected its approach, or knew something it did not.
Will it slow my agent down?
No. Uploads run in the background on a timer. 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 takes the hooks out of every agent's settings and leaves your agents' own files exactly as they were.
Get paid for the sessions you already run
macOS or Linux. Takes about a minute.