Ruflo reads configuration from three sources that compose at runtime: a JSON config file for structured settings (swarm topology, MCP transport, memory backend), a dotenv file for secrets and runtime flags, and a Claude Code settings file that registers hooks. You can use all three together or just the ones your use case requires — most projects start with onlyDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/ruvnet/ruflo/llms.txt
Use this file to discover all available pages before exploring further.
.env and claude-flow.config.json.
Configuration Files
| File | Purpose |
|---|---|
claude-flow.config.json | Core config: swarm topology, MCP server, memory backend, provider routing |
.env | Secret keys, provider API keys, and feature flags (never commit this file) |
.claude/settings.json | Hook registration, Claude Code experimental settings, agent-teams flags |
Core Configuration Schema
claude-flow.config.json lives at your project root. The full schema with commonly used fields:
swarm
swarm
| Key | Type | Description |
|---|---|---|
topology | "hierarchical" | "mesh" | "ring" | "star" | Agent coordination pattern. hierarchical (default) puts a queen coordinator in charge of workers — recommended for structured coding tasks because it enforces goal alignment at every step. |
maxAgents | number | Maximum simultaneous agents. Keep at 6–8 to minimize coordination overhead and drift surface. |
consensus | "raft" | "byzantine" | "gossip" | "quorum" | "crdt" | Distributed decision algorithm. raft (leader-elected, f < n/2) is the default for strongly consistent state; byzantine (2/3 supermajority, f < n/3) for adversarial environments. |
mcp
mcp
| Key | Type | Description | |
|---|---|---|---|
transport | "stdio" | "http" | "websocket" | ”http” | “websocket”` | Transport mode. stdio (default) is used by Claude Code and Codex — no network port is opened. Use http or websocket for editors that connect over a network socket. |
port | number | HTTP or WebSocket transport port (default: 3000). Ignored when transport is stdio. | |
host | string | Bind host for HTTP/WebSocket transport (default: "localhost"). | |
toolGroups | string[] | Restrict which tool groups are loaded. Fewer groups = faster startup and lower token usage. Options: coordination, memory, monitoring, github, system. |
memory
memory
| Key | Type | Description |
|---|---|---|
backend | "hybrid" | "sqlite" | "hnsw" | hybrid uses SQLite + HNSW index together. HNSW provides sub-millisecond vector search; SQLite handles relational persistence. |
dimensions | number | Embedding vector dimensions. Default 384 (matches ONNX MiniLM). OpenAI’s text-embedding-3-large uses 3072. |
cacheEnabled | boolean | Enable LRU embedding cache. Cache hits return in <1ms. |
providers
providers
| Key | Type | Description |
|---|---|---|
default | "claude" | "openai" | "google" | "cohere" | "ollama" | Primary LLM provider. |
fallback | string | Provider to use when the default is unavailable or rate-limited. |
Configuration by Use Case
- Minimal
- Standard
- Enterprise
Core CLI only — no ML dependencies, no HNSW, no ONNX. Fastest install (~45 MB, ~15s). Suitable for scripting, plugin authors using Install with:Or use the install script flag:
CLI_CORE=1, or environments where you don’t need vector memory.Install Profiles
| Profile | Flag | Size | Time | Use Case |
|---|---|---|---|---|
| Minimal | --omit=optional or --minimal | ~45 MB | ~15s | Core CLI only, no ML/embeddings |
| Default | (none) | ~340 MB | ~35s cold-cache | Full install with HNSW, ONNX, neural features |
The minimal install includes all CLI commands and the MCP server. What’s missing is the local ONNX embedding runtime, HNSW indexing, and neural features. Vector memory falls back to SQLite brute-force search and the OpenAI embedding API (if
OPENAI_API_KEY is set) rather than local ONNX SIMD.CLI Config Commands
Ruflo ships aconfig subcommand for reading and writing claude-flow.config.json from the terminal:
Precedence Order
When the same setting appears in multiple places, Ruflo resolves conflicts in this order (highest wins):- CLI flags (e.g.,
--transport http,--tools=coordination) - Environment variables (e.g.,
CLAUDE_FLOW_MCP_PORT) claude-flow.config.json- Built-in defaults
Next Steps
Environment Variables
Complete reference for API keys, memory paths, MCP settings, and the
CLI_CORE fast path.MCP Server
Start the MCP server, configure transports, register with editors, and explore tool groups.
