Version control built for agents.

ryke is a clean-slate VCS where AI agents are first-class operators — structured output, conflict-as-data, and parallel workspaces that don't step on each other.

Git was built for humans.

Agents don't read diffs on a screen — they parse them. They don't resolve conflicts in an editor — they need conflicts as data. They don't work alone — hundreds of them touch one repo at once. ryke starts from these facts instead of retrofitting them.

Your agent runs it. Not parses it.

Every ryke command answers in typed, structured JSON — no porcelain scraping, no regex archaeology.

agent — ryke

Conflict-as-data

Merges never explode into text markers. Conflicts are structured data your agent can inspect, resolve — or ship as-is.

Parallel agent workspaces

Hundreds of agents, one repository, zero stepped-on toes. Workspaces are cheap, isolated, and mergeable.

A machine-first API

Every operation returns typed, structured output. No porcelain parsing. Agents speak ryke natively.

Provenance built in

Every change knows who made it — human or agent — and why. Review and trust at agent speed.

Conflicts, minus the markers.

The same merge, twice: what Git hands your agent — and what ryke hands it.

git — text markers

fn plan(&self, batch: usize) {
<<<<<<< HEAD (agent-17)
    self.queue.fill(batch)
=======
    self.queue.fill_ordered(batch)
>>>>>>> feat/agent-42
}

ryke — structured data

{
  "path": "core/scheduler.rs",
  "ours":   { "call": "fill",         "by": "agent-17" },
  "theirs": { "call": "fill_ordered", "by": "agent-42" },
  "overlap": "call-site",
  "resolvable": "machine"
}

A hundred agents. One repository.

Workspaces are cheap and isolated — they fan out, work in parallel, and converge without stepping on each other.

Where this is going

Now
Core engine — private alpha

Conflict-as-data, parallel workspaces and the machine-first API — hardened with early users from this waitlist.
Next
Hosted platform

ryke.ai becomes the home for your repositories — provenance and review built in from day one.
Later
The agent ecosystem

Review, trust and collaboration at agent speed — for teams where humans and agents ship together.

Questions, answered

What is ryke?

A clean-slate version control system whose data model and API are built for AI agents first. Humans stay welcome — agents are the primary operators.

Who is it for?

Teams and builders who run coding agents at scale and are tired of retrofitting Git: structured output, conflict-as-data and parallel workspaces are the defaults here, not plugins.

What happens after I join the waitlist?

We contact you about early access in signup order, starting with the private alpha of the core engine. Nothing else — no newsletter, no tracking.

What do you store about me?

Your email address, your language preference and the consent version — nothing more. Deletion is one reply away.

Version control is about to change.

Join the waitlist and be first in line for the private alpha.