clode: Claude Code, everywhere

When your OS isn't popular or your computer isn't recent, how do you run Claude Code?

Download clode to your fastest machine, then build quaudes for your whole collection:

mv clode-* clode && chmod +x clode
for i in darwin-arm64 darwin-ppc netbsd-sparc linux-s390x windows-x64; do
  ./clode build --target $i --out quaude-$i
done

quaude-darwin-arm64 and quaude-windows-x64 might not be that interesting. Claude Code already ships for those platforms. But quaude-darwin-ppc, quaude-netbsd-sparc, quaude-linux-s390x?

For the complete list of targets:

clode build --list-targets

Have fun.

What? How?!?

This repo contains no Anthropic code, only a tool that, by request:

1. Fetches upstream claude (nearest match for your target OS and arch)
2. Extracts its embedded JavaScript
3. Rebases Bun-specific calls onto Node equivalents
4. Backs Node API with (mostly) txiki.js
5. Compiles to QuickJS-NG bytecode
6. Writes quaude

(If your host is Node-compatible and you want that runtime instead, clode build --naude writes naude, replacing steps 4 and 5 with an embedded Node interpreter.)

Runtime dependencies

Quaude shells out to these for tool use:

• bash for basic tool use
• bfs >= 3.x (built with Oniguruma)
• ugrep >= 7.5.0

clode fetch (downloading and verifying the upstream bundle) additionally needs:

• a SHA-256 tool — one of sha256sum, shasum, gsha256sum, sha256, cksum, openssl, or digest (or set CLODE_SHA256)
• tar, gzip, and unzip to extract downloads

Updating

Run clode fetch and clode build again.

Beware

Some features are at least temporarily missing: computer-use, image/sharp, audio capture, runtime TypeScript, MSAL, and perhaps other Bun.* stubs.

clode is a hilarious hack that will inevitably stop working. It attempts to be reasonably robust against many failure modes, but can't possibly defend against all of them. Run quaude on your weird computer while you still can.