ArgosBrain vs Roo Code

What Roo Code is

The baseline, stated fairly.

Roo Code (formerly Roo Cline; Apache-2.0) is a Cline fork with Custom Modes (Architect, Code, Ask, Debug, + user-defined). It ships no first-party memory.

The de-facto standard is the community project GreatScottyMac/roo-code-memory-bank (and successor RooFlow), which layers a smaller memory-bank on top, with .roorules-<mode> files dictating which files each mode reads/writes.

How it actually works

Technical facts.

StorageCommunity MD convention.
RetrievalSame prompt-stuffing as Cline, but mode-scoped writes (Architect writes decisionLog.md, Code writes activeContext.md).
CostRoo's apply_diff is ~30% cheaper than Cline's full-file rewrites (independent benchmarks); memory-bank loading cost is comparable.
LimitationsCommunity-maintained; open issue #40: "Should there be a Standard for memory banks?"

Sources: Custom Modes docs · Memory Bank repo

Verdict

Where each one wins.

↑ Where ArgosBrain wins

Official, engineered, benchmarked — not a community convention.
Same wins as vs Cline — $0 retrieval, symbol precision, hash staleness.

↑ Where Roo Code wins

Custom Modes are a product-shaped idea we don't have.
Kilo Code fork ($8M seed, late 2025) signals category momentum.

When to choose which

Honest recommendation.

Choose Roo Code if

You want mode-scoped agent behavior
The Cline/Roo convention fits your workflow

Choose ArgosBrain if

Roo for the modes + ArgosBrain for the memory engine