Ruflo plugin
Plugin marketplace and CLI for Claude Code: agent swarms, background workers, vector memory, security review and test generation
- 80,113 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Installs hooks and a background daemon that run agents without user input
- Agents change code and run commands across several worktrees
Install
- Works in
Manual install
/plugin marketplace add ruvnet/ruflo
/plugin install ruflo-core@ruflo
/plugin install ruflo-swarm@rufloOther plugins install the same way, for example ruflo-rag-memory@ruflo.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Installs hooks and a background daemon that run agents without user input
- Agents change code and run commands across several worktrees
This is third-party code. Review the repository files before installing.
What it does
Ruflo, formerly claude-flow, adds multi-agent coordination to Claude Code. Its marketplace offers separate plugins: ruflo-core with an MCP server, ruflo-swarm for agent teams in isolated worktrees, ruflo-loop-workers for scheduled background tasks, ruflo-rag-memory with vector search, plus plugins for security audits, tests and docs. The full install via npx ruflo init scaffolds agents, commands, skills, hooks, an MCP server and a daemon into the project. The README clearly separates the lightweight plugin path from the full CLI path.
Who it is for. For developers who want to run several coordinated agents in Claude Code and automate background work.
Good fit when
- You want to split a task across several agents
- You need long-term memory across sessions with semantic search
- You want recurring background security or test coverage checks
Not a fit when
- One agent and stock Claude Code are enough
- You cannot add .claude and .claude-flow folders to the repository
Example request
Start a swarm of three agents: one writes the API, one writes tests, one reviews securityLimitations
The full install writes many files into the project, including CLAUDE.md, settings and hooks. Plugins other than ruflo-core do not register an MCP server, and tool names differ from the CLI track. The project is large and fast-moving; some plugins are experimental.
How to disable. Uninstall plugins via /plugin uninstall. After a full install, delete .claude-flow and the files added to .claude, and remove the ruflo MCP server from settings.
FAQ
Plugins or npx ruflo init?
Plugins write nothing into the project and suit a trial. The full install adds hooks, a daemon and all tools but also adds files to the repository.
Is this the same project as claude-flow?
Yes, the README badges point to ruvnet/claude-flow; development continues under the Ruflo name.
Discussion
No questions or reviews yet.
Related
PluginsMulti-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
A Claude Code plugin marketplace with ready sets of agents, slash commands, hooks and skills, plus a search site
A set of /sc slash commands, agents and behavior modes for Claude Code, from brainstorming and research to implementation and tests
Workflows for Claude Code: /do, /omo, /bmad-pilot and more commands, with Codex, Gemini or OpenCode writing the code through codeagent-wrapper
A Claude Code plugin marketplace: slash commands, subagents, MCP servers and hooks installed with /plugin
One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
README in short
The README opens with a table of two install paths: Claude Code plugins with no project changes, and the npx ruflo init CLI with the full set of agents, commands, skills, MCP and hooks. It lists plugins by group: orchestration, memory, security, tests, docs and more. It also explains how MCP tools are named in each path. MIT licensed.