Product

Clade Code
Cost-honest savings
for Claude Code

One install, one init. Every claude session in every folder routes through Clade Code. Typical workloads see ~60–80% real cost reduction — measured per-call, reported honestly.
01

Real savings. Honestly reported.

Most tools tout "99% saved" without saying which calls they count. Clade Code measures every call against an honest baseline — the Monitor panel's number is what you actually saved.

Typical workload
~60–80% saved
on real Claude Code sessions. Read-heavy and rename-heavy workflows save more.
02

How it works

Clade Code installs as a local MCP server that Claude Code talks to — the same way in a terminal and in VS Code. Mechanical, verifiable work runs on a local model on your Mac; anything genuinely hard is handed straight back to Claude Code. You keep one assistant — the cheap parts just stop costing tokens.

Claude Code your Max session MCP Clade Code local · on your Mac local model mechanical · ~free hard work  →  handed back to Claude Code THE SAME ENGINE — BOTH SURFACES ›_ CLI terminal — every claude session clade-code on · off VS Code Monitor panel — live savings offload  On / Off
One local MCP layer · same routing in CLI and VS Code · hard work always returns to Claude Code
03

Install — three steps

One-time setup. macOS Apple Silicon. No Python. No package manager. No marketplace dependency.

Step 1 — Download

# clade-code CLI — notarized, stapled installer package
curl -fsSL -L https://github.com/tacticscale/clade-releases/releases/download/clade-code-v0.1.123/clade-code-0.1.123-macos-arm64.pkg -o clade-code.pkg

# VS Code extension (Token Savings Monitor)
curl -fsSL https://imlore.com/clade/releases/clade-0.1.203.vsix -o clade.vsix

Step 2 — Install

# install the CLI (stapled — no network check, no Gatekeeper prompt)
sudo installer -pkg clade-code.pkg -target /

# sideload the VS Code extension
code --install-extension clade.vsix

Step 3 — Init — this is the step that turns Clade Code on

# Register clade-code with Claude Code and enable delegation
# for your account. One-time, runs from any directory; settings apply
# to every project from now on (no per-folder setup).
clade-code init

After clade-code init (run once), every claude session in any terminal, in any project folder, automatically routes eligible small tasks to Clade Code. The VS Code Monitor panel shows live savings per project; opening it is optional. State lives at ~/.clade/state.json — a single file for your whole account, not per-workspace.

Verify with clade-code --version (→ clade-code 0.1.123). No API keys. No account. No runtime dependencies. Everything runs locally after install.

Updates are manual: re-run the same curl + code --install-extension + clade-code init with newer version filenames to upgrade. The VS Code marketplace is not used; the extension is sideloaded directly.

04

Uninstall — clean removal

Reverses everything init set up. Run clade-code uninstall first — it de-registers from Claude Code, so removing the binary never leaves broken hooks behind.

# 1. de-register from Claude Code — removes the MCP entry + the clade hooks.
#    Run FIRST: it needs the binary present. (keeps ~/.clade; --purge deletes it)
clade-code uninstall

# Then remove the two add-ons in reverse install order (last in, first out):
# 2. the VS Code extension (installed last)
code --uninstall-extension imlore.clade

# 3. the CLI binary + its installer receipt (installed first)
sudo rm -rf /usr/local/lib/clade-code /usr/local/bin/clade-code
sudo pkgutil --forget com.imlore.clade-code

Order matters — clade-code uninstall needs the binary present to run, so do it before the rm. Claude Code keeps working; only the Clade wiring is removed.

Real savings. Honestly reported.

Clade Code reduces Claude API costs on real Claude Code sessions and reports the savings honestly, per call. The number on the Monitor panel is what you actually saved — measured, not estimated. One install, one init, every project.