Introduction

ver (from the Latin ver, “spring”) is an intuitive, easy-to-use, and non git-like version control system. It tracks your files as content-defined chunks, stores them in a content-addressable blob store, and syncs to S3, GCS, or Azure Blob Storage.

What you can do

Snapshot a project with ver snap full and restore it with ver goto. There is no staging area and no branches.
Keep several contexts for the same project (local disk, S3, GCS, Azure) and move snapshots between them with ver sync.
Merge two diverged copies of a project with a three-way merge and interactive conflict resolution.

Get started with your agent

Point your coding agent at ver’s agent-readable documentation index and let it install and set up ver for you:

Install and set up ver from https://ver-vcs.net/llms.txt

Get started manually

Install
```
cargo install ver-vcs
```
Initialize ver globally
```
ver ctx init --global
```
This creates ~/.ver/, where your contexts live.
Scaffold a local context
```
ver ctx scaffold myproject --fs local --kv embedded
```
Then edit ~/.ver/contexts.toml to fill in the paths, switch to the context with ver ctx switch myproject, and run ver ctx init inside it.
Take a snapshot
```
ver snap full --name my-first-snapshot
```

Where to next

Concepts: contexts, snapshots, chunks, and how ver stores your data.
Snapshotting: full and partial snapshots, restoring, history.
Syncing: replicate a context to another backend.
Merging: reconcile diverged histories.
CLI reference: every command and flag.