AI agents, orchestrated by specs

Spec → code

Orchestrate Claude Code, Codex, or OpenCode through specs, parallel worktrees, and acceptance reviews.

Spec-drivenParallel worktreesAcceptance gate
$ cargo install cflx
$ cflx run add-search-filter
proposal → apply → acceptance → merge

Watch the demo

Quickstart

How the workflow feels in practice

A pragmatic flow for teams that want automation with guardrails, not magic hidden behind a single prompt.

01

Create a change proposal

Use the bundled cflx proposal skill to generate proposal.md, tasks.md, and spec deltas in an OpenSpec change directory.

02

Run locally or as a server

Start the TUI with cflx or launch headless execution with cflx run. Use server mode when you want the browser dashboard.

03

3. Let apply and acceptance iterate

Implementation, verification, and acceptance move through tight loops with minimal context handoff.

04

4. Promote the result

Archive, resolve, and merge successful changes so the product grows as a sequence of validated increments.

Conflux workflow from analysis through apply, acceptance, archive, and resolve

Questions teams ask before adopting it

The short answers that unblock an evaluation quickly.

Is Conflux itself a coding agent?+

No. Conflux is the orchestrator. It launches and coordinates external coding agents such as Claude Code, Codex, or OpenCode.

When is it a better fit than using one CLI agent directly?+

Use Conflux when you need persistent change tracking, parallel execution, review separation, or a workflow that continues after the original prompt ends.

Can I monitor runs remotely?+

Yes. Server mode and the Web UI expose a dashboard, WebSocket state updates, and REST endpoints for monitoring and automation.

Start with a real Conflux run today.