ruvnet/ruflo

Get started with Ruflo

/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.

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.

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.

_{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.

---

One task: create a mission with Claude

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 separate workflow animation uses sample data; neither is evidence of completed swarm work or memory recall.

Implementation and recorded test findings · Reproduction script

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

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

| | Claude Code Plugin | CLI install (npx ruflo init) | |---|---|---| | What it gives you | Slash commands + a few skills + agent definitions per-plugin | Full Ruflo loop — 98 agents, 60+ commands, 30 skills, MCP server, hooks, daemon | | Files in your workspace | Zero | .claude/, .claude-flow/, CLAUDE.md, helpers, settings | | MCP server registered | Only if ruflo-core is installed (it ships its own .mcp.json) — most other plugins don't | Yes | | Hooks installed | No | Yes | | Best for | Try a single plugin's commands without committing to the full install | Production use — everything works as documented |

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.

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 platform
npx ruflo@latest init wizard
Quick non-interactive init
npx ruflo@latest init
Or install globally
npm 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.

MCP Server

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

---

What You Get

| Capability | Description | |------------|-------------| | 100+ Agents | Specialized agents for coding, testing, security, docs, architecture | | Comms Layer | Zero-trust federation — agents across machines/orgs discover, authenticate, and exchange work securely | | Swarm Coordination | Hierarchical, mesh, and adaptive topologies with consensus | | Self-Learning | SONA neural patterns, ReasoningBank, trajectory learning | | Vector Memory | HNSW-indexed AgentDB — measured ~1.9x faster at N=20k, ~3.2x–4.7x at N=5k vs brute force (recall@10 ~0.99); ANN wins above the crossover, ties/loses at small N. See audit + scripts/benchmark-intelligence.mjs | | Background Workers | 12 auto-triggered workers (audit, optimize, testgaps, etc.) | | Plugin Marketplace | 33 native Claude Code plugins + 21 npm plugins | | Multi-Provider | Claude, GPT, Gemini, Cohere, Ollama with smart routing | | Security | AIDefence, input validation, CVE remediation, path traversal prevention | | Agent Federation | Cross-installation agent collaboration with zero-trust security | | MetaHarness | Audit your AI agent setup before you ship. Grade readiness (1-100), scan tool configs for security issues, snapshot the whole project to catch regressions over time, and find templates that match your repo. ruflo eject turns a ruflo project into a standalone agent toolkit with its own name. Full guide. |

Learning from experience

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

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 lay