What it does¶
Define teams of AI agents in YAML. fuseraft-cli drives them through a coordinated pipeline — from planning to implementation to review — until the task is done.
-
Agent teams as YAML
Define each agent's name, model, system prompt, and plugins in a single YAML config. The coordinator routes work between them automatically.
-
Model-agnostic
Mix frontier LLMs and local SLMs per agent in the same team — Anthropic, OpenAI, Google, Mistral, xAI, DeepSeek, Azure OpenAI, or any model served through Ollama. Rotate API keys automatically on rate limits.
-
Rich plugin ecosystem
Every agent can call filesystem, shell, git, HTTP, JSON, search, and Docker sandbox tools out of the box. Connect any external MCP server.
-
Resilient sessions
Sessions checkpoint after every turn. Interrupt anytime and resume exactly where you left off — no work is lost.
-
Spec-driven development
Use
--specto anchor the team to an agreed specification before implementation begins. Routing validators block handoffs until evidence is present. -
Governance & cost control
Track token usage and estimated cost per turn. Enforce hard spending caps. Apply execution rings, prompt injection detection, and a hash-chain audit log.
Quick start¶
Then run the setup wizard on first launch:
No configuration found at ~/.fuseraft/config
Provider setup
Configure your provider and API key, then pick a model.
Provider URL (http://localhost:11434): https://api.anthropic.com/v1
API Key (leave blank for Ollama): ••••••••
Model (2 available from https://api.anthropic.com/v1)
> claude-sonnet-4-6
claude-opus-4-6
>
Generate a team config and run your first task:
fuseraft init
fuseraft run -c .fuseraft/config/orchestration.yaml "Add a hello-world endpoint to this project"
Documentation¶
| Doc | What it covers |
|---|---|
| Getting Started | Prerequisites, installation, first run |
| Writing Effective Tasks | Task descriptions that produce correct, verifiable results |
| Spec-Driven Development | Using --spec to anchor agents before implementation begins |
| CLI Reference | All commands and flags |
| Configuration | Full config schema (YAML and JSON) |
| Models & Providers | Model configuration and auto-detection |
| Plugins | All built-in tools agents can call |
| Strategies | Selection and termination strategies |
| Routing Validators | Anti-hallucination handoff guards |
| Harness Engineering | Building configs that enforce correctness mechanically |
| MCP Integration | Connecting external MCP servers |
| Security & Sandbox | File and network containment |
| Governance | Execution rings, audit log, circuit breaker, SLO tracking |
| Evals | Running agent teams against scored test cases; CI integration |
| Sessions | Resumption, HITL, cost tracking, compaction |
| Context Management | How fuseraft manages context across a long session |
| Context Store | Importing reference material for agents |
| Skills | Portable skill packages and cross-session skill index |
| Examples | Ready-to-use config examples |
VS Code Extension¶
The Fuseraft VS Code extension brings the CLI into your editor — run tasks, browse sessions, validate configs, and get YAML/JSON IntelliSense, all from the activity bar.