Pre-compiled, cross-platform binaries for the eight VIMS agent shells, keyed on each upstream project's commit SHA. Built weekly on this public repo's GitHub Actions; consumed by VIMS and anyone else who wants reproducible shell runtimes without a 90-minute cold compile.
| Shell | Upstream | Language |
|---|---|---|
| openclaw | https://github.com/openclaw/openclaw | TypeScript / Node |
| zeroclaw | https://github.com/zeroclaw-labs/zeroclaw | Rust |
| nanoclaw | https://github.com/qwibitai/nanoclaw | TypeScript / Node |
| nemoclaw | https://github.com/nvidia/nemoclaw | Python (NeMo) |
| mirofish | https://github.com/mirofish/mirofish | Python (PyInstaller) |
| picoclaw | https://github.com/sipeed/picoclaw | Go |
| hermes | https://github.com/nousresearch/hermes-agent | Python (pipx) |
| openfang | https://github.com/openfang/openfang | Rust (Tauri) |
darwin-arm64 · darwin-amd64 · linux-amd64 · linux-arm64 · windows-amd64
NanoClaw is the exception. NanoClaw v2 is a checkout-rooted app (it reads
package.json, templates/ and container/ from its working directory and
builds its agent image from that tree), so a single-file binary cannot run it.
Its nanoclaw-<target> asset is a gzip'd tar of the built tree (dist/ plus
node_modules), which VIMS unpacks and stages one root per instance from.
node_modules holds per-platform optional dependencies, so the tree is built
natively only: linux-amd64, linux-arm64, darwin-arm64. NanoClaw does not
run on Windows, and there is no darwin-amd64 build.
Each release is <shell>-<sha12> where <sha12> is the first 12 chars of
the upstream commit. The release contains one asset per platform:
openclaw-a3b2c1d4e5f6
├── openclaw-darwin-arm64
├── openclaw-darwin-amd64
├── openclaw-linux-amd64
├── openclaw-linux-arm64
└── openclaw-windows-amd64.exe
git ls-remote https://github.com/openclaw/openclaw HEAD | cut -f1 | head -c 12SHA12=a3b2c1d4e5f6
curl -fL -o openclaw \
https://github.com/HelloVIMS/Runtimes/releases/download/openclaw-$SHA12/openclaw-linux-amd64
chmod +x openclawgh release download openclaw-$SHA12 \
--repo HelloVIMS/Runtimes \
--pattern 'openclaw-linux-amd64'The full build matrix runs on schedule a weekly schedule and on manual dispatch. Per-shell SHA-keyed cache means re-runs against unchanged upstreams are near-instant.
gh workflow run build-runtimes.yml --repo HelloVIMS/Runtimes
gh workflow run build-runtimes.yml --repo HelloVIMS/Runtimes \
-f only=mirofish,openfang # rebuild a subsetMost shells are built from upstream unmodified. Where VIMS needs a change
upstream hasn't taken, the build applies patches/<shell>/*.patch to the
fresh checkout (apply_runtime_patches in scripts/update-runtimes.sh). A
patch upstream has merged is skipped automatically; one that stops applying
fails the build instead of shipping an unpatched runtime.
| Shell | Patch | Why |
|---|---|---|
mirofish |
0001-configurable-data-dir.patch |
MIROFISH_DATA_DIR for projects, simulations and reports, so the packaged binary keeps them across restarts (upstream PR 666ghj/MiroFish#923) |
mirofish |
0002-vims-zep-base-url.patch |
VIMS_ZEP_BASE_URL: lets VIMS run MiroFish's memory graph on the VIMS knowledge base when no Zep Cloud key is configured. Unset, MiroFish talks to Zep Cloud exactly as upstream does |
nanoclaw |
0001-vims-gateway-provider.patch |
A vims credential-gateway provider (NANOCLAW_GATEWAY_PROVIDER=vims): agent containers reach models only through the VIMS daemon's Anthropic route with the instance's VIMS token, and VIMS picks the model (local vLLM or a Key Manager key). Inert unless selected |
nanoclaw |
0002-cli-turn-ack.patch |
The CLI channel acknowledges each chat line with its inbound id ({"accepted": …}) and marks edits with operation/messageId, so a programmatic client (VIMS) can tell an edit of an earlier message from a reply to the one it sent. Extra lines/fields only; terminal clients ignore them |
Release tags still name the upstream commit; a patched shell's binary is that commit plus its patches.
Binaries are redistributed under each upstream project's original license.
This repo's workflow + scripts are MIT (see LICENSE). Verify the license
of the specific shell you redistribute.
These binaries are reproducible from the commit SHA referenced in the release tag. Build provenance is recorded in each release's notes (CI run URL + timestamp).