Release History of Ruflo: From v1.0.1 to v3.5.0

Ruflo evolved from an initial AI-agent orchestration tool in January 2025 through three major architectural iterations to a stable, production-ready platform released as v3.5.0 in February 2026.

The release history of Ruflo (formerly developed under the claude-flow namespace) is documented across multiple changelog files in the ruvnet/ruflo repository. This timeline tracks the project's rapid evolution from a monolithic CLI tool to a modular, MCP-first agentic orchestration system.

Early Foundations: The v1.x Series (January–May 2025)

The initial development phase established core AI-agent orchestration capabilities and CLI infrastructure.

v1.0.1 (January 1, 2025)

The first public release introduced the core AI-agent orchestration system, CLI interface, and initial SPARC integration. This version established the foundation for swarm-based task execution.

v1.0.28 (January 10, 2025)

Added project-management commands, monitoring capabilities, and orchestration templates. This release expanded the CLI with administrative tooling for managing agent deployments.

v1.0.50 (March 15, 2025)

Introduced Swarm & SPARC support, enabling parallel task execution and background workers. This version marked the transition from single-agent to multi-agent coordination.

v1.0.71 (May 1, 2025)

Delivered the full CLI command set, cross-platform support, and complete SPARC full-stack integration. This was the final v1.x release before the architectural transition to V2.

Transition to V2: Alpha Series (May–October 2025)

The V2 development cycle focused on Windows/WSL compatibility, safety systems, and the introduction of the agentic-flow coordination engine.

v2.0.0-alpha.33 (May 15, 2025)

Addressed Windows/WSL compatibility issues, fixed module import problems, and introduced a comprehensive test suite. This alpha stabilized cross-platform support.

v2.0.0-alpha.53 (June 1, 2025)

Implemented the Hook Safety System, hive-mind optimization, and neural-link safety protocols. This release introduced critical safety guardrails for agent coordination.

v2.0.0-alpha.128 (August 10, 2025)

Delivered mature hive-mind optimization, robust database schema, and auto-rebuild capabilities for native SQLite bindings. This alpha stabilized the memory backend.

v2.7.0 (August 20, 2025)

Marked the deep integration with the agentic-flow coordination engine and introduced a modular installation strategy. This version established the architectural pattern carried into V3.

v2.7.34 (October 5, 2025)

Added PostgreSQL bridge support with attention mechanisms and GNN (Graph Neural Network), neural persistence features, and multi-platform CI/CD pipelines.

V3 Alpha Series: Architecture Overhaul (October 2025–January 2026)

The V3 series represented a complete architectural rewrite, introducing a modular monorepo structure, MCP-first APIs, and the @claude-flow/* package ecosystem. Development occurred in the v3/ directory with its own v3/CHANGELOG.md.

v3.0.0-alpha.1 (October 1, 2025)

Split the monorepo into 10 independent @claude-flow/* packages, introduced 215 MCP tools, and implemented a 15-agent hierarchical mesh. Added Flash-Attention and SONA integration for hardware-accelerated inference.

v3.0.0-alpha.50 (October 15, 2025)

Delivered the full V3 implementation with coordinator consolidation, event-sourcing architecture, agent-DB migration tools, and an auto-update system (ADR-025).

v3.0.0-alpha.100 (November 20, 2025)

Introduced the @claude-flow/guidance control plane, a Rust-WASM policy kernel, the ContinueGate safety gate, and a 22-benchmark performance suite.

v3.0.0-alpha.150 (November 30, 2025)

Added SONA & SemanticRouter integration, memory-namespace support, and MCP-tool naming fixes for Claude Desktop compatibility.

v3.0.0-alpha.170 (December 10, 2025)

Launched the Plugin Marketplace with 8 official plugins and IPFS registry support, the Gas Town bridge, and 10 RuVector WASM plugins.

v3.0.0-alpha.184 (December 25, 2025)

Overhauled CLI help categorization, introduced a curl-style installer script, and optimized packages for SEO.

v3.0.0-alpha.1 (January 4, 2026)

A major architecture overhaul with 10 ADRs (Architecture Decision Records), Flash-Attention speed-ups (2.49–7.47×), HNSW search improvements (150–12,500×), and 83% memory reduction. Included major security hardening.

Rebranding to Ruflo: Stable Release (February 2026)

The project officially rebranded from claude-flow to Ruflo, consolidating the V3 architecture into a stable, production-ready release.

v3.5.0 (February 27, 2026)

The first stable Ruflo release marked the completion of the rebrand, integrating agentic-flow v3, 215 MCP tools, and comprehensive security hardening (CVE-1/2/3 patches). This version introduced the health-check doctor and reported zero known vulnerabilities.

v3.1.0-alpha.55 (February 27, 2026)

Integrated AgentDB v3.0.0-alpha.9 with 8 controllers and a mutation-guard proof engine, added new MCP tools, and fixed a GNN crash.

v3.1.0-alpha.43 (February 15, 2026)

Fixed CLI branding to use ruflo instead of claude-flow and resolved a Windows ESM import crash.

v3.1.0-alpha.36 (February 10, 2026)

Ensured hook backward-compatibility, fixed Windows npm install crashes, and bumped agentdb.

v3.1.0-alpha.29 (February 1, 2026)

Applied security fixes, introduced Agent Teams hooks, and added a settings flag for the upgrade command.

How to Check Your Ruflo Version

You can verify which version of Ruflo is installed using the CLI or by reading the package manifest programmatically.

CLI Version Check

# Check version via npx (no install required)

npx ruflo --version

# Example output

ruflo/3.5.0 node/v20.12.0 linux/x64

Programmatic Version Access

import { readFile } from 'node:fs/promises';
import { join } from 'node:path';

async function getRufloVersion() {
  const pkgJson = await readFile(
    join(import.meta.dirname, '../package.json'), 
    'utf8'
  );
  const { version } = JSON.parse(pkgJson);
  return version;
}

getRufloVersion().then(v => console.log(`Running Ruflo v${v}`));

Source: package.json in the repository root.

Accessing Release Notes via GitHub API

curl -s https://api.github.com/repos/ruvnet/ruflo/releases \
  | jq '.[] | {tag_name, published_at, name, body}'

Summary

• Ruflo began as Claude Flow in January 2025 with v1.0.1, introducing core AI-agent orchestration and SPARC integration.
• The v2.x series (May–October 2025) focused on cross-platform stability, safety systems, and the agentic-flow coordination engine.
• V3 (October 2025–January 2026) represented a complete architectural overhaul with a modular monorepo (@claude-flow/* packages), MCP-first APIs, Flash-Attention acceleration, and HNSW vector search.
• The project officially rebranded to Ruflo with the stable release of v3.5.0 on February 27, 2026, featuring zero known vulnerabilities and comprehensive security hardening.
• Release history is documented in CHANGELOG.md (root) and v3/CHANGELOG.md, with version metadata available in package.json.

Frequently Asked Questions

What is the current stable version of Ruflo?

The current stable version is v3.5.0, released on February 27, 2026. This version represents the first stable release under the Ruflo brand name, featuring zero known vulnerabilities, 215 MCP tools, and full agentic-flow v3 integration.

How do I migrate from Claude Flow to Ruflo?

Migration involves updating your CLI commands from claude-flow to ruflo and ensuring your configuration files reference the new package namespace. Version v3.1.0-alpha.43 (February 15, 2026) specifically addressed CLI branding fixes to ensure smooth transition. Run npx ruflo doctor to verify your installation health after migration.

Where can I find detailed release notes for V3 alpha versions?

Detailed release notes for the V3 alpha series are located in v3/CHANGELOG.md within the repository. This file documents the monorepo split into @claude-flow/* packages, architectural decisions (ADRs), and performance metrics such as Flash-Attention speed-ups and HNSW search improvements. The root CHANGELOG.md covers stable releases and v1/v2 history.

What major architectural changes occurred between V2 and V3?

V3 introduced a modular monorepo architecture with 10 independent @claude-flow/* packages, replacing the monolithic structure of V2. Key changes included MCP-first APIs (all functionality exposed via Model-Context-Protocol tools), Flash-Attention hardware acceleration (2.49–7.47× speedup), HNSW vector search (150–12,500× improvement), and a hybrid memory backend combining SQLite with AgentDB.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}