Opt-in AI workflow data · CLI pilot

Get paid for the AI work you’re already doing.

Install a lightweight collector, work in a capture session with the CLI agents you use today, review what’s included, and get paid once when you finalize a contribution. Turnset packages privacy-preserved datasets for model builders—you keep control.

How it works
  • Opt-in only
  • Review before finalize
  • One-time payment

Why this exists

Millions of AI interactions happen daily—especially in CLI coding agents with multi-turn, tool-using workflows. That data improves systems and creates value. Contributors rarely participate in that value. Turnset changes that with consent, review, and pay.

How it works

Four steps. No ambient logging story—capture sessions you start.

  1. 01

    Install

    Download the Turnset collector. CLI-first for the pilot—PTY/proxied shell capture.

  2. 02

    Capture

    Start a capture session and work normally with Claude Code, Codex, OpenCode, and other supported CLIs.

  3. 03

    Review

    Inspect captured turns. Remove anything you don’t want included before finalization.

  4. 04

    Finalize & earn

    Finalize the contribution. One-time payment when it’s accepted—pilot terms apply.

You’re in control

  • Opt in only No capture unless you start a session.
  • Pause / revoke anytime Stop contributing whenever you want.
  • Review before finalization Nothing ships without your sign-off.
  • Remove interactions Drop turns you don’t want in the package.
  • Transparent history Contribution and payout status in one place.
  • Vendor neutral Keep the CLI stack you already use.

Built for CLI power users

Pilot targets developers running agent CLIs in the terminal—not desktop IDEs yet.

  • Claude Code
  • Codex
  • OpenCode
  • OpenClaw
  • Hermes
  • Gemini CLI
  • OpenRouter agents
  • + more

Desktop capture (Cursor, VS Code) is on the roadmap. This pilot validates supply on CLI first.

Privacy

  • You decide to participate—capture sessions are explicit.
  • You can stop whenever you want.
  • Sensitive information is scrubbed before packaging.
  • Contributions are privacy-preserved before licensing—not “fully anonymized” marketing.
  • We license packaged datasets to organizations. We don’t sell your identity as the product.

FAQ

Why would anyone pay for this data?
Model builders need real multi-turn, tool-using workflow traces with clear rights and provenance—not scraped or synthetic-only supply.
What exactly is collected?
AI workflow traces from your capture session: prompts, responses, tool calls, and related context needed to represent the workflow. Not whole-disk or ambient OS logging.
How does the collector work?
CLI-first: a local collector wraps or proxies your shell session during capture. You start and stop sessions explicitly.
Can I remove interactions?
Yes. Review window before finalization—remove anything you don’t want included.
How do payouts work?
One-time payment when a contribution is finalized and accepted under pilot terms. No royalty ledger in v1.
Which tools are supported today?
Pilot focuses on CLI agents (Claude Code, Codex, OpenCode, OpenClaw, Hermes, Gemini CLI, OpenRouter-backed CLIs). Desktop IDEs come later.
Who buys the data?
Model builders, research teams, and enterprise AI teams—packaged datasets with provenance, not raw user dumps.

Join the CLI pilot

Request access. We’re onboarding developers who live in the terminal.

Request pilot access

CLI developers first. We’ll email when your cohort opens.

No spam. Unsubscribe anytime.