Raven (EverMind)
Workflow & Automation · tested 2026-10-02 · re-test due 2027-01-02 · by the Hlido desk, not the vendor
In short: A multi-agent orchestration layer that sits above the coding agents you already run (Claude Code, Codex, Copilot, Qwen and more) — real GitHub traction and broad interop, wrapped in heavy 'self-evolving / RSI' language that the surface can't back up.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
Raven (EverMind) scores 70/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-10-02). STEADY (70) rests on two real signals: broad, concretely-named interop across the major coding agents, and visible GitHub traction (~5k stars) that most new entrants do not have. Pricing: Open source (free entry point documented).
Raven, from EverMind, bills itself as 'the Harness of Harnesses' — a self-evolving multi-agent orchestration ecosystem that interprets a goal, assembles the right specialists, and keeps every handoff visible across a long list of agents you might already use (Claude Code, Codex, GitHub Copilot, Qwen Code, Grok, Kimi, and its own Raven variants). It installs on macOS/Windows via a curl one-liner and is on GitHub with a visible ~5,000-star count, which is a genuine, if early, traction signal that most entrants lack. Hlido's read: the core idea — one surface that routes a goal across whatever harnesses you have and makes the orchestration legible — is a real and useful abstraction, and the breadth of named integrations suggests actual interop work rather than vapor. What Hlido discounts is the framing. 'Self-evolving', 'Built for RSI' (recursive self-improvement) and 'Harness of Harnesses' are large claims that a landing page cannot substantiate, and Hlido did not install Raven, run an orchestration, or verify that the handoffs, presets or 'self-evolution' behave as described. Two practical notes for adopters: a 'curl | bash' installer warrants the usual scrutiny before running, and the real test of an orchestrator is reliability under multi-step handoffs, which only a hands-on run reveals. Credible and unusually well-connected for its stage; the grand self-improvement language is marketing until proven.
Why STEADY
STEADY (70) rests on two real signals: broad, concretely-named interop across the major coding agents, and visible GitHub traction (~5k stars) that most new entrants do not have. It is held at the STEADY floor rather than higher because the flagship 'self-evolving / RSI / Harness of Harnesses' framing is unverified, Hlido did not run it, and confidence is low on a single-surface read — orchestration reliability can only be judged hands-on.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Every agent, one surface' — multi-agent orchestration
- PASS Cta present (required) — Install one-liner + 'View On GitHub'
- PASS Pricing or access — Free install via curl + public GitHub; no paid tiers captured
- PASS Evidence or demo — 'See in run' section + public repo; not exercised by Hlido
What it does well
- Clear, useful abstraction: one surface that routes a goal across the harnesses you already run and keeps handoffs visible
- Broad, concretely-named interop (Claude Code, Codex, GitHub Copilot, Qwen Code, Grok, Kimi and its own Raven variants)
- Visible GitHub traction (~5,000 stars) — a real early-adoption signal
- Cross-platform install (macOS/Windows) with presets to lower the starting effort
What it fails at
- 'Self-evolving' / 'Built for RSI' / 'Harness of Harnesses' are large claims unsupported by the public surface
- Not installed or exercised by Hlido — orchestration reliability, handoff quality and 'self-evolution' are unverified
- 'curl | bash' install path warrants security scrutiny before running
- No pricing/limits or data-handling detail captured from the surface
Red flags
- Markets 'self-evolving' and 'Built for RSI' (recursive self-improvement) — strong claims not substantiated on the public surface; verify hands-on before relying on them
- Primary install is a 'curl | bash' one-liner — review the script before executing
Best for
- Developers already juggling multiple coding agents who want a single orchestration surface over them
- Teams that value visible handoffs and presets when composing multi-agent workflows
- Early adopters comfortable evaluating a fast-moving open project hands-on
Not recommended for
- Teams needing a stable, supported orchestrator with documented reliability guarantees
- Security-conservative environments uneasy with a curl-pipe installer
- Buyers who would take 'self-evolving / RSI' claims at face value without testing
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
- Pricing findable on the public surfacePASS Free install via curl one-liner and public GitHub repo; no paid tiers shown on the surface (tested 2026-10-02)
Derived from Hlido-held evidence only (public-surface capture + editorial text); not vendor-supplied; re-derived daily. Verify current terms in the project's repository. Last verified 2026-10-02.
Agent relevance
CLI Behavioral-testable
Raven is itself an agent-orchestration layer: installed via CLI (curl one-liner), it drives and coordinates other coding agents you already run. Open on GitHub and installable, so it is behaviorally testable by running it; no separate API/MCP surface is advertised for an outside agent to drive Raven itself.
Agent-friendly score: 7/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Orchestrates/routes goals across multiple existing agents (Claude Code, Codex, Copilot, Qwen, etc.) — source (2026-10-02) verified
- Installable on macOS/Windows; public GitHub repo with ~5,000 stars — source (2026-10-02) verified
- Self-evolving / built for recursive self-improvement (RSI) — source (2026-10-02)