An agent meta-harness for Claude Code and Codex.

Get started with Ruflo

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.

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.

Compare install paths · Open the console · User guide

Optional: ruOS Desktop

Connect ruOS to ChatGPT or Claude via MCP:

https://ruos.cognitum.one/mcp

npx ruvector

Ruflo

English · 简体中文

📖 RuFlo Explained — Build an AI Team That Plans, Remembers, Tests, and Improves A 14-chapter guide: from the basic idea to a first useful task, then memory, agent teams, plugins, cost and verification.

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.

User → Ruflo (CLI/MCP) → Router → Swarm → Agents → Memory → LLM providers. Memory feeds useful experience back into routing. This is a conceptual flow, not a live execution trace.

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.

Claude Flow is now Ruflo — named by rUv, who loves Rust, flow states, and building things that feel inevitable. The "Ru" is the rUv. The "flo" is working until 3am. Underneath, powered by Cognitum.One agentic architecture, running a supercharged Rust-based AI engine, embeddings, memory, and plugin system.

Your agent cockpit. Track workflows, agents, models, tokens and cost beside Claude Code. The animation shows startup checks and a sample workflow, not a live session.

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.

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

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 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):

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