Sorrelalpha

Developer preview · v0.1.0-alpha.2

Version control for work that happens in parallel.

Sorrel gives humans and AI agents a shared foundation for isolated work, focused context, portable execution, and policy-aware collaboration—without cutting ties with Git.

Start building Explore the source
License
MIT / Apache-2.0
Core
Rust
Adoption
Git-compatible
workspace / checkout live graph
main
agent / auth
agent / docs
snapshotbaseline
change_8f2token scopes
change_c41runner guide
✓
merged cleanly3 independent changes
$ sorrel lane list 3 active
Content-addressedLocal-firstPolicy-nativeOpen sourceGit-compatible
01 / THE MODEL

A different unit of work

Branches track code.
Lanes track intent.

Agentic development creates more than diffs. It creates parallel context, delegated authority, runtime needs, and review boundaries. Sorrel models those concerns directly, then turns the result back into portable history.

01

Lanes

Isolated, resumable streams for humans and agents—with explicit heads and clean merge semantics.

sorrel lane create
02

Slices

Focused dependency closures that share enough context to work, without sharing the entire repository.

sorrel slice create
03

Runners

Portable job bundles for local processes, containers, and future user-owned compute.

sorrel workflow run <job>
04

Vault

Secret references, scoped grants, injection, and redacted logs—never credentials inside patch text.

sorrel secret get <name>
02 / ARCHITECTURE

Composable by design

A foundation,
not a walled garden.

Core owns durable truth. The collaboration layer coordinates it. Git remains the interoperability boundary.

04
Sorrel HubProposals · reviews · projects · coordination
collaborate
03
Lanes · Slices · Runners · VaultAgent workspaces · context · jobs · secret references
orchestrate
02
Sorrel CoreObjects · snapshots · changes · merge · policy
persist
01
Git compatibilityImport · export · colocated sync · migration
interoperate
S

The policy spine

Authority flows from prior authority.

Peers, runners, Hub, and remotes accept permission changes only through an already-authorized chain. An agent cannot grant itself more power by editing a file.

03 / WORKFLOW

From blank directory to shared work

Familiar commands.
Stronger semantics.

Start local. Add structured changes. Split work into lanes. Connect a Hub only when collaboration needs it.

Read the getting started guide
quickstart.shzsh
# Create a content-addressed workspace
$ sorrel init

# Record intent, not just bytes
$ sorrel change create -m "add auth policy"

# Isolate delegated work
$ sorrel lane create --name agent-auth
$ sorrel push origin

✓ 12 objects transferred
✓ lane/agent-auth updated
04 / STATUS

Developer preview

Real foundation.
Deliberately early.

Sorrel’s local VCS, Git bridge, sync transport, and development Hub are working today. The alpha is for exploration and controlled development—not production infrastructure.

Working now

  • Persistent local object store and history
  • Lanes, stacks, and three-way merge
  • Git import, export, and colocated sync
  • SecretSpec injection and redacted run logs
  • Hub sync, proposals, and review flows

Still ahead

  • Production Hub authentication
  • Richer review UX and merge queues
  • Hosted secrets and run streaming
  • Stable embedding surface
  • Desktop and mobile applications
Full statusRelease notesDocumentationAPI reference

Build with us

The next workflow
won’t fit in the last one.

Sorrel is open source and building in public.

View on GitHub Get started