Leep

An open-source, server-centric version control system built for repositories where most commits come from AI agents and CI. Inspired by Anthropic's Scion, Meta's Mononoke and Zed's DeltaDB. Git-compatible through an import/export bridge. Agent provenance (agent.model, agent.session) is queryable: leep log --agent-model M, leep blame --who, leep provenance. Code is searchable on the server without a checkout: leep search -i -E 'fn\s+main'.

Status: early development (v0.1).

• Architecture
• Formats and compatibility
• Decision records
• Roadmap
• Deploying with Docker
• Operating: logs and metrics
• Runbooks: what to do when an alert fires
• The leep command line: exit codes and the agent contract
• Using Leep from AI agents (MCP)
• Contributing and the agent guide

Layout

• crates/leep-core: data model, storage traits, HTTP API types
• crates/leep-store: blob storage backends (filesystem, S3/MinIO, LRU cache)
• crates/leep-meta: metadata backends (SQLite, Postgres)
• crates/leep-derive: derived data and repository operations
• crates/leep-server: the leep-server HTTP server
• crates/leep-cli: the leep command-line client
• crates/leep-mcp: the leep-mcp MCP server for AI agents (docs/MCP.md)
• crates/leep-git: git import/export and the live git mirror (leep-git mirror)
• crates/leep-fuzz-targets and fuzz/: fuzz targets (docs/FUZZING.md)

Build

cargo build --release     # every crate, including test and benchmark tools
cargo test

To run a server without Docker, build only the shipped binaries and follow DEPLOY.md, "Without Docker".

Docker

docker build -t leep:dev .
docker run -p 127.0.0.1:7070:7070 -e LEEP_INSECURE_NO_AUTH=1 -v leep-data:/var/lib/leep leep:dev

See docs/DEPLOY.md for the Postgres compose stack and S3 storage.

License

Apache-2.0; see LICENSE. To report a security problem, see SECURITY.md. Changes are recorded in CHANGELOG.md.