Official site: openflows.dev
OpenFlows is an autonomous software development team that runs itself.
Give it a GitHub repo and some issues, and OpenFlows handles everything — writing code, opening PRs, reviewing changes, merging, and documenting — without you writing a single line of code.
# Stable release
curl -fsSL https://raw.githubusercontent.com/The-AgenticFlow/openflows/main/scripts/install.sh | bash
# Or edge (pre-release from main)
curl -fsSL https://raw.githubusercontent.com/The-AgenticFlow/openflows/main/scripts/install.sh | bash -s -- --edgeThen set up and run:
openflows-setup # interactive wizard — configures repo, API keys, CLI backend
openflows # start the autonomous team# Stable release
npm install -g @the-agenticflow/openflows
# Edge (pre-release)
npm install -g @the-agenticflow/openflows@nextThen:
openflows-setup
openflowsgit clone https://github.com/The-AgenticFlow/openflows.git
cd openflows
# Build and install release binaries
make install # installs to ~/.local/bin
openflows-setup
openflowsOr build manually with Cargo:
cargo build --release -p openflows
# Binaries at target/release/{openflows,openflows-setup,openflows-dashboard,openflows-doctor}
# You also need the orchestration/ directory — copy it to ~/.local/bin/ or set OPENFLOWS_HOME
cp -r orchestration ~/.local/bin/OpenFlows runs a team of AI agents that collaborate just like a real engineering team:
You create a GitHub issue → The team picks it up → Code is written, reviewed, and merged → You get a PR
You stay in the loop only when needed — security concerns, ambiguous specs, or major decisions. Otherwise, the team runs autonomously.
| Agent | Role | What it does |
|---|---|---|
| NEXUS | Orchestrator | Assigns issues, coordinates the team, notifies you when needed |
| FORGE | Builder | Writes code, creates branches, opens PRs |
| SENTINEL | Reviewer | Reviews code for security, quality, and test coverage |
| VESSEL | DevOps | Monitors CI, handles merge conflicts, squash-merges green PRs |
| LORE | Writer | Documents decisions, updates changelogs, maintains project history |
| Requirement | Version | Notes |
|---|---|---|
| Git | 2.x+ | Required for repo cloning, worktree management, and branching |
| Node.js | 18+ | Required for the GitHub MCP server (npx -y @modelcontextprotocol/server-github) |
| C compiler | — | build-essential (Debian/Ubuntu) or xcode-select --install (macOS) |
| OpenSSL dev headers | — | pkg-config + libssl-dev (Debian/Ubuntu) or brew install openssl (macOS) |
| Rust | 1.70+ | Only required if building from source (cargo install openflows) |
- A GitHub repository — the repo OpenFlows will work on
- A GitHub Personal Access Token — with
reposcope (set asGITHUB_PERSONAL_ACCESS_TOKEN)
| Mode | CLI | Required API Key | Install |
|---|---|---|---|
| Claude + Anthropic | Claude Code | ANTHROPIC_API_KEY |
npm install -g @anthropic-ai/claude-code && claude login |
| Codex + OpenAI | Codex | OPENAI_API_KEY |
npm install -g @openai/codex && codex login --with-api-key |
| Codex + Fireworks | Codex | FIREWORKS_API_KEY |
npm install -g @openai/codex && codex login --with-api-key |
Set DEFAULT_CLI to claude or codex to select your backend.
| Service | Purpose | Default |
|---|---|---|
| Redis 7 | Persistent state across restarts | In-memory (state lost on restart) |
| LiteLLM proxy | Per-agent model routing, cost optimization, rate limits | Direct API calls |
Both are included in the Docker Compose stack (docker compose up).
cp .env.example .env
# Edit .env with your tokens and API keysThe openflows-setup wizard handles configuration interactively. See .env.example for all available options.
| Guide | What it covers |
|---|---|
| INSTALL.md | Full installation options and configuration |
| RUN.md | Running and configuration reference |
| TUTORIAL.md | Step-by-step walkthrough with logs |
| CONTRIBUTING.md | How to contribute to OpenFlows |
| BUILD.md | Building from source |
| DEMO.md | Quick demo (no API keys needed) |
MIT