Skip to main content

Routa Docs

Workspace-first agent coordination
Routa orchestration logo

Turn a Kanban board into an execution surface for AI teams.

Routa is a multi-agent coordination platform for software delivery. It combines a workspace-first UI, Kanban automation, and protocol bridges across ACP, MCP, A2A, and AG-UI so you can route real implementation work through specialized agents instead of a single monolithic assistant.

Next.js web runtime
Tauri desktop shell
Rust Axum backend
Kanban-first automation

What Routa Is For

Routa is built for teams that want agent workflows to stay inspectable, testable, and operable. Instead of letting one long-running chat own everything, Routa makes work explicit:

  • a workspace holds codebases, memory, sessions, and automation state
  • a Kanban board becomes the control surface for decomposition and handoff
  • specialists are attached to stages like backlog refinement, implementation, review, and reporting
  • protocol adapters let external agent runtimes join the flow without changing the product model

Documentation Map

Platform Surface

Coordinator

Routa plans, routes, and observes work. The coordinator owns intent decomposition and keeps the board, sessions, and tooling aligned.

Execution Lanes

Backlog, Todo, Dev, Review, and Done can each bind to a specialist so lane transitions become operational triggers rather than passive status changes.

Protocol Bridges

ACP manages agent processes, MCP exposes coordination tools, A2A covers federation, and AG-UI supports richer agent-generated interface patterns.

Quickstart

npm install --legacy-peer-deps
npm run dev

Open http://localhost:3000.

To run the desktop shell as well:

npm --prefix apps/desktop install
npm run tauri:dev

To run the Rust backend directly:

cargo run -p routa-server

If you are running against a custom backend endpoint, set:

ROUTA_RUST_BACKEND_URL="http://127.0.0.1:3210"
npm run dev

CLI

The Rust CLI binary is routa. Install it from crates.io, from the current checkout, or build it without installing:

cargo install routa-cli
cargo install --path crates/routa-cli
cargo build --release --manifest-path crates/routa-cli/Cargo.toml

Run a quick one-off DEVELOPER session from a single requirement:

routa -p "Add OAuth login with Google and GitHub providers"
routa -p "Refactor the auth module" --workspace-id my-project
routa -p "Investigate flaky tests" --provider claude

Prompt mode uses:

  • --workspace-id <ID>: target workspace, default default
  • --provider <PROVIDER>: ACP provider for the developer session, default opencode
  • --db <PATH>: SQLite database path, default routa.db

Start the local Routa backend server:

routa server --host 127.0.0.1 --port 3210
routa server --static-dir ../../out

Run Routa itself as an ACP server over stdio:

routa acp serve --workspace-id my-project --provider opencode

Useful ACP runtime commands:

routa acp list
routa acp installed
routa acp install opencode
routa acp runtime-status
routa acp ensure-node
routa acp ensure-uv

Execute a specialist directly or run a coordinated team session:

routa specialist run crafter -p "Implement a calculator CLI"
routa specialist run ui-journey-evaluator -p "scenario: core-home-session"
routa team run -t "Design and implement Kanban automation" --workspace-id default
routa team status --workspace-id default

Validation Basics

npm run lint
npm run test:run

Core Usage

Web

Use the home page to create or enter a workspace, connect a repository, and route a new requirement into the board-driven workflow.

CLI

Top-level commands from routa --help:

server      Start the Routa HTTP backend server
acp ACP server and runtime management
agent Agent lifecycle and specialist execution helpers
specialist Run specialist definitions directly
task Task CRUD and artifact operations
kanban Board, card, and column management
workspace Workspace management
skill Skill discovery and reload
session Persisted ACP session inspection and picking
rpc Send raw JSON-RPC requests
delegate Delegate a task to a specialist agent
chat Interactive chat with an agent
scan Repository static/security scans
workflow YAML-defined workflow execution and validation
review Read-only code review analysis against git changes
team Team coordination with an agent lead

Common CLI workflows:

routa workspace list
routa workspace create --name my-project

routa agent list --workspace-id default
routa agent create --name dev-agent --role DEVELOPER --workspace-id default
routa agent run --specialist crafter -p "Add auth middleware" --workspace-id default

routa task list --workspace-id default
routa task create --title "Add feature" --objective "Implement user authentication" --workspace-id default
routa task update-status --id <task-id> --status COMPLETED --agent-id <agent-id>
routa task artifact-provide --task-id <task-id> --agent-id <agent-id> --type logs --content "build ok"
routa task artifact-list --task-id <task-id>

routa session list --workspace-id default
routa session get --id <session-id>
routa session pick --workspace-id default

routa kanban card create --title "Investigate release flow" --workspace-id default --board-id <board-id> --column-id <column-id>
routa kanban card move --card-id <card-id> --target-column-id todo

routa workflow validate .routa/workflows/release.yaml
routa workflow run .routa/workflows/release.yaml --verbose

routa chat --workspace-id default --provider opencode --role DEVELOPER
routa scan --project-dir . --output-dir artifacts/security
routa review --help
routa delegate --task-id <task-id> --caller-agent-id <parent-agent-id> --caller-session-id <session-id> --specialist CRAFTER --provider opencode

FAQ

  • If a provider command is missing, install provider CLI first (opencode, claude, etc.).
  • If Tauri dependencies are missing, install desktop dependencies with npm --prefix apps/desktop install.
  • If static build fails, check Node version and run from repo root.

Demo