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
  • Pi
  • OpenCode

One command

Set up in a minute. Then forget it.

The script installs one self-contained binary and runs benchturn init: sign in with GitHub, connect every coding agent on the machine, and offer the sessions you already have.

There are no tasks to pick up and nothing to annotate. Uploads run in the background on a timer, and your agent never slows down.

zsh~/code 

      

    

  


  

    

      

        
How it works

        
Real work, turned into environments.

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

      

      

        
01
You work as usual
Each prompt you send to a connected agent inside a git repository is captured: the tree before and after, and the transcript of that turn.

        
02
We review every session
Is it a real project, real code changed, a task that can be checked? The good ones are rebuilt as reproducible environments. The rest are deleted.

        
03
Labs license, you get paid
When a lab buys an environment built from your session, your share goes to your pending payout. benchturn account shows it all.

      

    

  


  

    

      

        
Privacy

        
What leaves your machine, and what never does.

      

      

        

          
What is recorded

          
For each prompt inside a git repository.

          
    
            
  • The repository's tree before the prompt and after the agent stops, so the change replays exactly.
    • 
            
  • The transcript of that turn: your prompt, the agent's messages, 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, and again on ours.

          
    
            
  • Keys, tokens, passwords and .env files. A capture that trips the secret scan is dropped, not uploaded.
    • 
            
  • Your name. A lab receives the public repository, the prompts and the transcript, nothing about your account.
    • 
            
  • Anything in a repository you excluded with .gen-ignore or benchturn ignore. Work outside git isn't recorded at all.
    • 
          

        

      

    

  


  

    

      

        
Where a session goes

        
From your terminal to a lab.

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

      

      

        
01
Received
Uploaded and on your portal.

        
02
Pending review
Judged on whether it can become an environment.

        
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.

      

    

  


  

    

      

        
The CLI

        
A handful of commands. That's the whole surface.

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

        
Read the docs

      

      

        

          
          
          
          
          
        

        
# Your own agent reads the sessions already on disk,
# picks the ones on public repos with real work,
# checks each for private material, and asks you.
# Nothing is uploaded until you say yes.
$ benchturn past

        
        
        
        
      

    

  


  

  

    

      

        
Questions

        
Asked and answered.

      

      

        
Do my old sessions count?
Yes. Run benchturn past and your own agent (Claude Code or Codex) finds the sessions already on disk, picks the ones that could qualify and shows you the list. Claude Code and Gemini CLI delete transcripts after 30 days by default; benchturn init turns that off.

        
What makes a session qualify?
A real project on a public repository, real code changed, and a task that can be checked: a bug fixed, a feature added, a refactor carried through. Best of all, you steered the agent. Private repositories can be recorded for you, but only sessions on public repositories become environments.

        
Does any agent need extra setup?
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.

        
Where does my data live?
Captures live on your machine under ~/.claude/gen until they are uploaded, and a copy stays there afterwards. benchturn delete removes one from both places. benchturn uninstall leaves your agents' own files exactly as they were.

        
How do I reach you?
Write to hello@benchturn.com. A Discord is coming soon.

      

    

  


  

    

      
Keep coding. Get paid for it.

      
One command. macOS or Linux, with git.

      

        
        Documentation