Auto-Company vs ruflo
A fully autonomous 'AI company' on your own PC: 14 expert-modeled agents ideate, decide, code, deploy and market 24/7 — driven by Claude Code or Codex CLI, with a local dashboard. — versus — ruvnet's 65k-star 'agent meta-harness': multi-agent swarms, adaptive memory and RAG layered over Claude Code, Codex and Hermes — npx ruflo, a UI beta, and a sprawling plugin ecosystem.
Same dream — an autonomous multi-agent operation driven through Claude Code/Codex — different scope: Auto-Company scripts 14 fixed expert roles; Ruflo is a general meta-harness you compose swarms from.
| Auto-Company | ruflo | |
|---|---|---|
| Stars | 2.1k | 66k |
| Forks | 317 | 7.8k |
| Language | Python | TypeScript |
| License | — | MIT |
| Last activity | 2 months ago | yesterday |
| Topics | agents, orchestration | agents, orchestration |
| Curated connections | 3 | 2 |
Auto-Company — the curator's take
The maximalist experiment: give 14 role-agents a company charter and let them run around the clock on your hardware. As a living demo of agentic workflows it's genuinely instructive — watch where autonomy compounds and where it wanders. Treat the 'without human intervention' framing as aspiration, NOT audit: unattended agents produce unattended mistakes at 24/7 speed, token bills to match, and there's NO license file at review time — check before building on it.
ruflo — the curator's take
The maximalist swarm layer (formerly claude-flow): hive-mind coordination, neural-sounding memory, 8M+ ecosystem downloads and a feature list that outruns most vendors — when it clicks, you get parallel specialist agents on your existing CLI subscriptions with one npx. Approach it like a curator: the marketing is louder than the documentation, benchmark claims are self-reported, and the ecosystem's size (plugins, sub-projects, rebrands) makes auditing what actually runs non-trivial. NOT for teams that need boring, inspectable orchestration — pick a small gated pipeline instead and add swarm ambition later. Run it in a sandbox first; form your own opinion of the hype-to-substance ratio.