Every number in the comparison table sourced and explained. Where data is community-reported rather than officially published, confidence is noted accordingly.
Workload assumption
All RAM figures assume a comparable workload. Actual usage scales with open tabs, file count, and active extensions.
CEF (Chromium 146) accounts for the majority of RAM. The Rust backend (agentmuxsrv-rs) itself uses ~15-40 MB. Agent processes (Claude Code, Codex CLI, etc.) are separate processes not included in this figure.
Download size is comparable to Warp (~205 MB) and less than Cursor (~230 MB). The key runtime difference from Electron is: no Node.js, no V8 GC in the backend, Rust ownership model prevents heap growth over long sessions.
Warp has not published official memory benchmarks.
Reported as non-reproducible by Warp team in some cases. Represents a known class of issue, not typical baseline.
Electron apps typically run 200-500 MB depending on renderer/process count.
Zed's own benchmarks. No independent third-party replication published.
Cursor's AI indexing and embedding features add significant memory overhead beyond VS Code baseline.
Represents worst-case scenarios. Not reproducible in all environments. Cursor has addressed some of these in recent releases.
Windsurf recommends 16 GB RAM system requirement in their docs.
Represents a specific configuration (large monorepo + full Cascade context). Not representative of typical use.
A note on AgentMux numbers
AgentMux is in early alpha. Our memory figures are self-reported from development builds and have not been independently benchmarked. We will update this page as the project matures and third-party benchmarks become available. We hold ourselves to the same sourcing standard as every other app listed here.
See a number that's wrong? Open an issue on GitHub.
github.com/agentmuxai/agentmux