Skip to content

Versi

Versi is a source control system built for the way software is starting to get made with AI agents.

Core trick

Records each saved file change into a durable line of work so an agent's disposable workspace can be deleted without losing its progress.

Tags

Description

Versi is a source control system built for the way software is starting to get made with AI agents. Git works well when a human edits code, stops, commits, and pushes. Agents do not work that way. They run in temporary sandboxes, get killed mid task, work across machines, and often make useful progress before there is a clean commit. Versi separates preserving progress from declaring meaning. Every saved file change can be recorded into a durable line of work, so an agent workspace can disappear without losing the work. Later, a human or agent can create checkpoints, run validation, compare approaches, and promote only the change that is ready. Our hackathon prototype shows the core primitive working end to end. We track saved file changes, sync them across separate local workspaces, create lines of work for parallel attempts, validate a checkpoint, rewind to a good state, promote the result to main, and resume from a fresh workspace through a remote store. The goal is not to replace Git for everyone. The goal is to build source control for parallel human and agent work, where workspaces are disposable but the work is not.
vsrikar08/versi★ 00 forksTypeScriptCreated Jun 14, 2026 · last push Jun 14, 2026

README excerpt

# Versi

Versi is an early product concept for agent-native source control. The core idea is to separate two jobs that Git currently combines:

- preserving progress continuously
- declaring meaningful history intentionally

The project is currently in the concept and prototype-planning stage. There is no implementation yet.

## Current Direction

The first prototype should prove save-based local change tracking before any hosting, remote sync, UI, merge workflow, or validation system is added.

The prototype question is:

```txt
Can Versi track save-based file changes in one local workspace, persist those changes, replay them, and synchronize them across two separate local workspace folders?
```

The local target shape is:

```txt
/tree1/
  project files

/tree2/
  project files

/.verse-local-sync/
  shared change store
```

## Docs

- [Versi concept](docs/versi-concept.md)
- [First prototype plan](docs/first-prototype-plan.md)

Team