Rufler banner
lib4u lib4u

Rufler

DevOps community

Description

🌊 The simple wrapper of leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

# Rufler

**One command. One YAML file. A whole autonomous AI swarm.**

`rufler` is a Python wrapper around [`ruflo`](https://github.com/ruvnet/ruflo) (the TypeScript AI agent orchestration CLI from the `claude-flow` family) that turns a dozen bootstrap commands into a single, declarative `rufler_flow.yml` file.

Instead of memorizing `ruflo init → daemon start → memory init → swarm init → hive-mind init → hive-mind spawn --claude --objective=...`, you write a YAML file that describes your project, your agent team and your task, and run:

rufler run

rufler handles preflight checks, daemon lifecycle, swarm/memory/hive-mind init, objective composition, logging, multi-task sequencing, AI-driven task decomposition, background supervision and live log following.


Why rufler and not ruflo directly?

`ruflo` is powerful but low-level. It exposes ~26 commands and 140+ subcommands that all have to be called in the right order with the right flags. For day-to-day driving of an autonomous Claude-Code swarm, that's a lot of ceremony.

Problem with raw ruflo How rufler fixes it
6–10 shell commands to boot a project (initdaemon startmemory initswarm inithive-mind inithive-mind spawn --claude --objective=...) One command: rufler run reads your YAML and runs the whole pipeline.
Objective prompt must be assembled by hand — project name, task body, every agent's role and prompt, autonomy flags Auto-composed objective from rufler_flow.yml — agents are sorted lead → senior → junior and injected into a single coherent prompt.
No native multi-task support — you spawn one hive per task manually Multi-task mode (task.multi: true) — run a list of subtasks sequentially or in parallel from one YAML.
No task decomposition **AI