Skip to main content

Quickstart

Get ferrus running against a project in under a minute.

1. Install​

|
iwr https://github.com/ferrus-dev/ferrus/releases/latest/download/install.ps1 -useb | iex

From crates.io:

cargo install ferrus

Or build from source:

git clone https://github.com/ferrus-dev/ferrus
cd ferrus
cargo install --path .

Requires Rust 1.95+. ferrus is currently alpha — expect rough edges.

2. Scaffold​

Inside any project directory:

ferrus init

This creates:

  • ferrus.toml — project config (check commands, limits, agent roles)
  • .ferrus/ — project-local templates, task/run artifacts, agent registry, and logs (gitignored)
  • ~/.ferrus/projects/<project-id>/ — machine-local project metadata and the ferrus.db SQLite database, which is the runtime source of truth
  • .agents/skills/ferrus*/ — skill files your coding agents will load to understand their role

3. Register your agents​

Tell ferrus which coding agent plays each role. Supported today: claude-code, codex, qwen-code (experimental), goose (experimental — convenient for local models), and opencode (experimental — supervisor/ reviewer role only for now).

ferrus register --supervisor claude-code --executor codex

This writes the right MCP server config (.claude/mcp-supervisor.json / .claude/mcp-executor.json for Claude Code, .codex/config.toml for Codex, .qwen/settings.json for Qwen Code, opencode.json for opencode) so agents automatically pick up ferrus serve as a tool server. goose needs no config file — ferrus attaches its role-scoped MCP server at launch instead. See Supported agents for backend-specific notes.

4. Drop into HQ​

Run ferrus with no arguments:

ferrus

You're now in HQ — a small interactive shell. Type / to see the available slash commands, or jump straight in:

ferrus> /task

A supervisor spawns, you describe what you want, and the full Executor → Reviewer loop runs automatically.

For larger features it's often worth drafting a written spec first:

ferrus> /spec

The supervisor walks you through a feature specification and saves it as Markdown under docs/specs/. You can then point the next /task at that file so the executor implements directly from an approved design. When every milestone in the spec is done, /archive-spec records an ## Outcome summary and files the spent task/run artifacts away — see the Specs & Milestones guide.

tip

Press Ctrl+C twice within 2 seconds to exit HQ.

What happens next​

ferrus> /task
  └─ supervisor → you describe the task → enqueue_task
       └─ executor (headless) → implements → check → submit
            └─ reviewer (headless) → reads submission → approve or reject
                 ├─ approved → Complete
                 └─ rejected → executor re-spawns with feedback

max_parallel_tasks in ferrus.toml controls how many tasks can have an executor running at once — each task advances independently through its own state.

Next, read about the state machine and the available HQ commands.