How it works · the signature mechanic

A push, end to end — and why only changed files cross the network.

The CLI fingerprints every local file and compares against what the server already has. It sends full content only for changed files; everything unchanged travels as a tiny reference. The network carries the delta, not the repo.

CLI Server Git Engine hash files · diff vs manifest PUT /push · changed files + hash-only refs authenticate · check write access forward lock · write blobs create commit · unlock result update metadata · record audit event PushResponse · save new manifest

Optimistic concurrency parent_sha

A push can say "I last saw version X." If another agent has pushed since, the server rejects it — catching conflicts at push time, not merge time.

Auto-create on first push

The first push to a new name creates the repo. No web setup, no separate creation step — one command from any directory.