Version, branch, and share vaults of files that are encrypted before they leave your machine. Zero knowledge: the server stores ciphertext, not your data.
Pure Python · two runtime dependencies · Apache-2.0
The vault key is the address, the auth, and the encryption key — one high-entropy string. Keep it safe.
sgit is git for encrypted vaults: clone, commit, branch, diff and merge folders of files that are encrypted with AES-256-GCM before they leave your machine.
resolve --show viewThat's the whole list — and we publish the threat model, including what the server can see (sizes, timing, vault ID). Read the security model →
Agents need shared state. Shared state needs versioning — and privacy. sgit is the encrypted, versioned workspace for humans and AI agents.
An agent clones it, reads and writes files normally, commits, pushes. The next session pulls and continues. State survives the context window.
Each agent gets its own private clone branch; work meets on named branches; a human reviews the merge — in the terminal or in the SG/Vault browser.
sgit write for surgical single-call commits, --json on every read path, cat --id with zero network calls, sparse clones for fast cold starts.
Durable, versioned state between sessions — encrypted end to end.
Read → Use caseAgents on their own branches, humans reviewing the merge.
Read → Use caseYou in the SG/Vault browser, the agent in the CLI — same vault.
Read → Use caseA shared folder the hosting provider cannot read, with rollback.
Read → Use casePKI: sign, verify, encrypt and decrypt files for named recipients.
Read →sgit is in beta, powering production workflows daily. No superlatives — just the evidence, and a page that tells you when not to use it.
Open source CLI. Free. Apache-2.0. pip install sgit-ai
Browse, edit and review the same vaults in the browser — an independent implementation of the same wire format.
The zero-knowledge storage service both clients speak to — the same server the integration tests run against.
Most of the thinking behind sgit no longer lives on this site. It moved out to
*.sgit.ai — a family of focused sites, each taking one question further than a
section here could, each with its own version history and repository. This site stayed about sgit.
The articles are the readable way in: one page, one argument, with the screenshots and the links to check it. If you only read one thing here, read one of these.