One binary. Exact provenance.
Install LimiLake without Python or a repository checkout. Every release carries its source identity, signatures, checksums, SBOMs, provenance, and version-matched Agent context.
Stable channel
v0.1.72
55defbcce3cfa20172238eaded03fa9a594fba53
curl -fsSL https://get.limilake.com/ | sh
limilake --output json versionLinux
AMD64
Linux
ARM64
macOS
Intel
macOS
Apple Silicon
Pin an exact release
Use immutable version selection for managed machines and reproducible setup.
curl -fsSL https://get.limilake.com/ | sh -s -- \
--version 0.1.72Update or roll back
Updates are explicit. Failed verification leaves the installed binary untouched.
limilake update --channel stable
limilake update --version <previous-version>Verify independently
Compare the release key and archive digests with the immutable GitHub Release audit. Repository access is currently required.
Immutable downloads
Audit the bytes for every target
Linux · AMD64
linux/amd64
sha256:f3316329875ed3f56463432d3fd1ab029739eba638a020405bca8cc5cfdff5bd
Linux · ARM64
linux/arm64
sha256:0524020077474ee7a6f17405fcbd6a982cfc33bb7a42ca6e70316243415e93b8
macOS · Intel
darwin/amd64
sha256:5de74e577c037084c7926f07ce5626d34fd045c0f53119c3a2f9da815a1e72c7
macOS · Apple Silicon
darwin/arm64
sha256:16168ee23a1ce2702f1cd5b5c87275004623e359fc9aa38920749c9c854fa683
After installation
Authenticate through device OAuth, then let the CLI discover the canonical Workspace repository. Native Git continues to own branches, fetch, pull, and push. Keep feature branches local, commit your changes, and push to the shared Draft as shown below. Human credentials can push only drafts/workspace and main; pushing main publishes the committed revision.
limilake auth login --host app.limilake.com --profile work
limilake workspace list
limilake workspace clone <workspace>cd <workspace>
limilake workspace doctor
git switch -c my-change
# Edit files, then stage and commit the intended changes
git push origin HEAD:drafts/workspace