Claude Flow

[Image] Get started with Ruflo

[Image] Start in Claude Code with core tools, the visual console and runtime mods. Requires Claude Code 2.1.287 or later. Run inside Claude Code:

/plugin marketplace add ruvnet/ruflo/plugin install ruflo-core@ruflo/plugin install ruflo-console@ruflo/plugin install ruflo-mods@ruflo/reload-plugins/ruflo

Core provides foundation tools. Console opens the agent cockpit. Mods add routing and policy enforcement inside Claude Code. Mods run with your account's permissions; review their code before installing.

[Image] Using Codex or another MCP enabled tool? Use NPX for Ruflo project setup and connect your client to the Ruflo MCP server. Run the setup wizard in your project terminal:

npx ruflo@latest init wizard

For clients that support local stdio MCP servers, configure command npx and arguments ["-y", "ruflo@latest", "mcp", "start"]. The equivalent server command is:

npx -y ruflo@latest mcp start

MCP exposes Ruflo tools to your client. The console and mods above are Claude Code integrations; hook support depends on the client.

[Image] Prefer a plain terminal? Optional. The console also runs on its own, with no Claude Code: npx ruflo tui (add --plain to print one frame for scripts). It shows Overview, Cost, Swarm, Events and Missions, plus an optional AI page. Terminal UI guide

[Looping recording of the optional ruflo terminal UI with its pictures: Overview in the Classic BBS look, the Orbital look with its moving globe, and the Swarm graph, in a sample project]

Compare install paths · Open the console · User guide

https://ruos.cognitum.one/mcp

npx ruvector

Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work. Ruflo is the harness — the execution layer around Claude Code and Codex that adds 100+ specialized agents, coordinated swarms, self-learning memory, federated comms across machines, and enterprise security guardrails. So agents don't just run, they collaborate.

One npx ruflo init gives Claude Code a nervous system: agents self-organize into swarms, learn from every task, remember across sessions, and — with federation — securely talk to agents on other machines without leaking data. You keep writing code. Ruflo handles the coordination.

[Ruflo trajectory learning: branching memory paths, outcome feedback, contrastive AI and local learning. No LLM required for local vector retrieval and contrastive updates; agent execution may still use an LLM.]

_{Conceptual learning loop. Local vector retrieval and contrastive updates can run without an LLM; embeddings and configured learning modules are still required. See the RuVector training integration and trajectory contrastive learning.}

New to Ruflo? You don't need to learn 314 MCP tools or 26 CLI commands. After init, just use Claude Code normally — the hooks system automatically routes tasks, learns from successful patterns, and coordinates agents in the background.

An origin you can inspect

[Claude Flow to Ruflo: founding idea on June 2, 2025, orchestration source on June 10, and the continuing Ruflo lineage.]

Built by Reuven Cohen (rUv), originally as Claude Flow. The first commit, June 2, 2025, describes a code orchestration layer for recursive agent cycles: Claude writes, edits, tests and improves. The June 10 source snapshot adds orchestration, task scheduling, memory and terminal modules.

A harness is the workbench around the model: it organizes tasks, carries context between steps and helps check results. This establishes Ruflo's lineage, not a universal first across every Claude Code tool. See the illustrated explainer, exact commits and earlier ecosystem context.

Grok Build: npx ruflo init --grok writes the project host surface (.grok/, the team bus, and the operator guide) and nothing outside the project; add --dry-run to preview. Setup, the spawn_subagent contract, the optional status row, and what to re-check when Grok updates: the Grok operator guide.

[Mission control: inspect agent work]

[Ruflo Orbital theme: animated boot checks, block logo, menu icons, rotating globe, swarm routing, six color palettes and responsive Theme Studio]

Open animated demo · Theme Studio guide · Workflow demo

[Image] Your agent cockpit. Track workflows, agents, models, tokens and cost beside Claude Code. The 38 second animation shows Orbital and Theme Studio through actual renderer frames, including boot checks, six palettes, customization, saved themes, JSON import and resizing. This compact 3.84 MB SVG retains all 456 frames. Native host and AI provider execution are not demonstrated.

[Image] Inspect any run. Open agent logs and results, search, triage failures, replay and compare. Start with npx ruflo init, restart Claude Code, then /ruflo. Full console tour.

[Image] Let Claude drive. You set the limits. Enable Settings → Claude control to navigate and run console actions. Choose read, write, manage or full, with ask or auto approval. The current default is read + ask; raising the level is your choice. Actions above your permission level are refused, and network, spending and destructive actions require confirmation even in auto. Review the live action log or press Take back control to stop Claude control. Details.

One task: create a mission with Claude

[Image] Watch the recorded console session below. Claude creates a mission, opens the Learning and Security pages, and reports its actions in Overview.

1. Set the boundary. Install the console using the commands below, open /ruflo, then choose Settings → Claude control → write + ask.
2. Give a concrete request. Try: “Create a mission to add a dark mode toggle. Show me the mission and its status.”
3. Approve creation. Claude opens Missions and sets the goal. Confirm the pending create action in the console.
4. Verify the result. Check that Missions contains the goal and Overview records the action. Creating a mission does not mean the feature has been implemented.
5. Keep control. Take back control pauses Claude's console tools. A later call should be refused until you restore control.

What the recording demonstrates: a real Claude Haiku session with write + auto, mission creation, page navigation, a refused swarm stop, and control being taken back. The steps above use ask so you approve creation yourself. The linked workflow animation uses sample data, while the theme demo replays renderer frames. Neither is evidence of completed swarm work or memory recall.

Implementation and recorded test findings · Reproduction script

[Claude Code with the ruflo console beside it: Claude sets a mission goal, creates the mission and opens the Learning, Security and Overview pages through the console tools; the Claude control dashboard logs each action; swarm-stop is refused because it needs the full level; the person clicks Take back control and the next request is refused]

Install the mods from the ruflo marketplace (Claude Code 2.1.287 or later; mods run with your account's permissions and are not sandboxed, so read the code first):

/plugin marketplace add ruvnet/ruflo/plugin install ruflo-console@ruflo/plugin install ruflo-mods@ruflo/reload-plugins

ruflo-console is the cockpit above, ruflo-mods routes prompts and enforces policy in-process, ruflo-swarm shows the swarm in a pane, and ruflo-ruos adds the ruOS status segment. Open /plugin to confirm they appear in the active mods line. Inside the console, /ruflo market is the Plugin Catalog: every ruflo plugin, mod and skill with what it ships, and buttons to install, enable, disable and update (each asks first).

Quick Start

[Start building with Ruflo]

There are two different install paths with very different surface areas. Pick based on what you need (#1744):

Path A — Claude Code Plugins (lite, slash commands only)

# Add the marketplace/plugin marketplace add ruvnet/ruflo
# Install core + any plugins you need/plugin install ruflo-core@ruflo/plugin install ruflo-swarm@ruflo/plugin install ruflo-rag-memory@ruflo/plugin install ruflo-neural-trader@ruflo

This adds slash commands and agent definitions. ruflo-core (installed above) does register its own MCP server on install — its tools are callable as mcp__plugin_ruflo-core_ruflo__* (e.g. mcp__plugin_ruflo-core_ruflo__memory_store), not the bare memory_store/swarm_init/agent_spawn names the CLI-track scaffold uses. Other plugins generally don't ship their own MCP server. For the full loop with the CLI-track tool names, use Path B below.

[Image] CLI Install

macOS / Linux / WSL / Git-Bash:

# One-line install (POSIX shells only — see Windows note below)curl -fsSL https://cdn.jsdelivr.net/gh/ruvnet/ruflo@main/scripts/install.sh | bash

All platforms (including native Windows PowerShell / cmd):

# Interactive setup wizard — runs identically on every platformnpx ruflo@latest init wizard
# Quick non-interactive init# npx ruflo@latest init
# Or install globallynpm install -g ruflo@latest

💡 Windows users: the curl ... | bash form needs a POSIX shell (Git-Bash, WSL, MSYS). The npx ruflo@latest init wizard line works natively in PowerShell and cmd. If you hit an 'bash' is not recognized error, use the npx line instead — both end up running the same init flow.

[Image] MCP Server

# Add Ruflo as an MCP server in Claude Codeclaude mcp add claude-flow -- npx ruflo@latest mcp start

What You Get

[Your agent toolkit]

[Image] Learning from experience

[Recall, execute, evaluate, store, adapt and reuse: an illustrative agent learning cycle.]

Useful trajectories and task feedback can inform future work. Results depend on the configured memory, learning components and quality of feedback. Learning plugin.

Agent Federation — Slack for Agents

[Connected intelligence across machines]

[Outbound agent, data filtering, signing and encryption, identity verification, input checks and receiving agent.]

Slack gave teams channels. Federation gives agents the same thing — shared workspaces across trust boundaries, where agents on different machines, orgs, or cloud regions can discover each other, prove who they are, and collaborate on tasks.

The difference: some channels are trusted, some aren't. @claude-flow/plugin-agent-federation handles that automatically. Your agents join a federation, get verified via mTLS + ed25519, and start exchanging work — with PII stripped before anything leaves your node and every message auditable. Untrusted agents can still participate at lower privilege: they see discovery info, not your memory. As they prove reliable, trust upgrades. If they misbehave, they get downgraded instantly — no human in the loop required.

You don't configure handshakes or manage certificates. You federation init, federation join, and your agents start talking. The protocol handles identity, the PII pipeline handles data safety, and the audit trail handles compliance.

📘 Full user guide: docs/federation/ — setup, MCP tools, trust levels, circuit breaker, and the (opt-in) WireGuard mesh layer that ties packet-layer reachability to federation trust. ADR-111 deep-dive at docs/federation/phase7-mesh-bringup.md.

# Team A: initialize federation and generate keypairnpx claude-flow@latest federation init
# Team A: join Team B's federation endpointnpx claude-flow@latest federation join wss://team-b.example.com:8443
# Team A: send a task — PII is stripped automatically before it leavesnpx claude-flow@latest federation send --to team-b --type task-request \  --message "Analyze transaction patterns for account anomalies"
# Team A: check peer trust levels and session healthnpx claude-flow@latest federation status

See issue #1669 for the complete architecture, trust model, and implementation roadmap.

# Claude Code plugin/plugin install ruflo-federation@ruflo
# Or via CLInpx claude-flow@latest plugins install @claude-flow/plugin-agent-federation

User --> Claude Code / CLI          |          v    Orchestration Layer    (MCP Server, Router, 27 Hooks)          |          v    Swarm Coordination    (Queen, Topology, Consensus)          |          v    100+ Specialized Agents    (coder, tester, reviewer, architect, security...)          |          v    Memory & Learning    (AgentDB, HNSW, SONA, ReasoningBank)          |          v    LLM Providers    (Claude, GPT, Gemini, Cohere, Ollama)

Documentation

[Guides, architecture and verification]

Four docs for four audiences:

Benchmark internals (for reproduction): sota-workload-spec.md · SOTA-PROGRESS.md · raw matrix JSON: darwin · linux

User Guide section index:

Support

[Build with the Ruflo community]

[Ruflo]

License

MIT - RuvNet

[Cognitum One: Ambient Intelligence at the edge of the Physical World. Explore cognitum.one.]