Zerostack 1.0: A Coding Agent That Uses 8MB of RAM. Not a Typo.

Most coding agents run on JavaScript runtimes and eat 300MB of RAM just sitting idle. Zerostack is built in pure Rust, uses ~8MB on idle, ~12MB while working, and posts 0.0% idle CPU. It hit 1.0 on crates.io this week with 474 points and 252 comments on Hacker News.

The architecture follows Unix philosophy: small composable tools instead of monolithic runtimes. Plan-then-execute loop. Up to 8 concurrent sub-agents for long-horizon tasks. The kind of engineering you'd expect from someone who thinks about resource budgets rather than throwing Node.js at everything.

Why this matters beyond the benchmarks: local agent execution is becoming a real deployment target. When you're running agents in CI pipelines, dev containers, or on developer laptops, the difference between 8MB and 300MB is the difference between running 30 agents and running 1. That math changes what architectures are practical.

I don't know yet whether Zerostack matches the feature depth of Claude Code or Codex CLI for complex workflows. The 1.0 version is focused on core coding loops, not the plugin ecosystem that more mature tools offer. But it's proof that the "agents must be heavy" assumption was a choice, not a constraint. And choices can be revisited.

The 252-comment HN thread is worth reading if you care about the tradeoffs. Real practitioners debating memory allocation strategies for agent workloads. That's the kind of conversation that happens when a tool challenges assumptions with data instead of marketing.