Anvaya Harness · THE EXECUTION LAYER
The LightestAgentic Harness.
One Rust binary, no runtime dependencies, 25.6 MB median RSS and 17x lighter than Claude Code. That weight is the point: it is why hundreds of agents fit on one machine. Run it as a full-screen TUI or headless in a pipeline, on your own hardware through Ollama (no account or key) or against Anthropic and OpenAI-compatible gateways when a task earns it. Every turn is packed with experience from Anvaya Mind → and reports back what it learned, the same graph Claude Code and other agents can read over MCP.
anv initanv -m devstral:latest -p ollamaProof
Ran 25 Agents on a 2008 Laptop.
In 2008, Intel shipped the Core 2 Duo. It was a good chip then.
In 2026, we ran 25 concurrent Anvaya agent sessions on a laptop with that chip and 4 GB of RAM. Arch Linux. No crashes. No faults.
Each headful session cost ~21 MB. Headless, ~16 MB. Baseline, ~9 MB. The old instruction set fought us, so we migrated memory allocators to get around it. The network card bottlenecked under 25 concurrent inference calls, so we wrote a Rust router to multiplex them.
The point is not that Anvaya runs on old hardware. The point is that if it runs 25 agents on a Core 2 Duo, it runs hundreds on your laptop. And it is all local.
Density
Hundreds of Agents. One Machine.
A 32-agent soak costs 103 MB total. 24 concurrent by default, 256 hard cap. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. On a modern laptop, that is hundreds, all local, all on your disk.
By The Numbers
What’s Actually In It.
Eight Screens, One Keystroke Apart.
Everything the agent is doing stays visible. The terminal panel runs a split-tree workspace, so you can keep a build running beside the agent without leaving the TUI.
Twenty-One Tools, All Native.
Every tool is compiled into the binary. Destructive ones route through an approval gate unless you pass --yolo; --plan-only disables writes and execution entirely.
Every Turn Is A Loop, Not A Prompt.
Between your input and the model sits a four-stage harness. The last two stages are what make experience compound, the loop closes back into Mind instead of ending at the reply.
It Runs Without You Watching.
Drop --no-tui and it becomes a normal Unix citizen: reads a prompt, writes to stdout, exits with a meaningful code. 0 on success, 1 on error, 2 when an approval was denied.
anv --no-tui --plan-only "what would change to add Redis caching?"anv --no-tui --yolo "fix the auth bug in src/auth.rs"anv -s listLightweight by measurement
Single-Digit MB At Idle. Milliseconds To Start.
Release build, macOS, footprint is truth (ps RSS includes mmap, excludes compressed pages, we print both). TUI idle ~5 MB footprint (12–15 MB ps RSS), headless setup ~3 MB, first frame in ~12 ms, idle CPU ~0% on 13 threads. A 17-hour live session held ~11 MB. Binary 14.3–18.7 MB depending on build, zero runtime dependencies. Measured 2026-08-14 protocol plus 2026-09-05 spot-check. The daemon side (warm ~50 MB, ingest bursts ~350 MB peak) lives in /benchmarks#footprint →
Run Agents That Fit On Your Laptop.
25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.
Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.