chained.tools

rusty

Rust toolchain written in Zig. Native resolve, lock, fetch, build, and test for a declared subset of Cargo. Fetch never shells out to cargo, and unsupported paths hard-error.

Open the repo Book a chat

Tool-driven

Large Rust monorepos suck.

They're better rusty.

$ rusty init myapp --cli -y --format rusty
$ rusty fetch
$ rusty build --workspace
$ rusty test -j 8

lock rusty.lock written
cas crates ingested, checksums held

Cargo was built for one crate at a time. The glue around it is rustup, scripts, and a lockfile nobody wants to regenerate on a clean machine. rusty is a dual-mode package manager and toolchain driver, hand-implemented in Zig, so the store and the compiler sit in one binary.

Two formats: Handwritten rusty-format resolves natively into rusty.lock. Cargo-format projects parse an existing Cargo.lock. Fetch never shells out to cargo. Missing lock fails closed.
Content store: rusty fetch ingests registry crates into a content-addressable store in parallel. When the lock already pins a checksum, the download skips a sparse-index lookup.
Supported hosts: Linux, WSL2, macOS Apple Silicon. Intel Mac and native Windows are out. On WSL2, keep the home on the Linux filesystem so hardlink and reflink still mean something.

Native build and test cover a declared subset of the Cargo surface. Unsupported paths hard-error. rusty auth is solved.gg / iResolved identity via clerk-zig. Nightly install lives in the repo.

The rest of the chain

All four

pyppi

Python toolchain in Zig.

gbrowse

Glass on the laptop, the rest in the cloud.

agentpass

The agent acts without seeing the secret.