Early Access. Commands and behavior can change between releases.
What it does for you
- Plans before it builds. The architect turns your request into requirements, a design and tasks. You approve the plan first.
- Builds and tests the change. The developer writes the code and its tests in your repository.
- Reviews with a fresh pair of eyes. A separate reviewer checks the work, so no agent approves its own change.
- Knows your project. Agents read your project context and engineering rules before they touch your code.
How it works
Your session is the orchestrator. It reads your project, hands each piece of work to the right agent and brings the results back to you. You talk to one session; the agents do the work behind it. Work moves through four steps: plan → build → review → land. You approve the plan and you approve the merge. Review can send work back to build until it passes. If you use a board, such as GitHub Projects, Architech reads your issues from it. Each planned issue becomes tasks, and each task becomes a reviewed pull request.The Software Factory
The Software Factory runs that lifecycle for your board: issues go in, reviewed pull requests come out. Run it on your machine from an Architech session, or on Mutagent Cloud, where each stage runs in its own sandbox. One file,factory.yaml, holds your board, repositories and approval rules.
You don’t need a Factory to use Architech. If you pick a board during onboarding, your project
gets a local
factory.yaml. Moving it to Cloud is a separate step you take yourself.Get started
- Install Architech.
- Run
architechin your repository. - Type
/onboard. Onboarding sets up your project context and engineering rules. A board is optional. - Describe a change, or type
/specto plan a feature.
Install Architech
Install the binary and start a session.
Orchestrator and agents
Who plans, builds and reviews your work.
Software Factory
Take an issue from plan to reviewed pull request.
Explore the features
Sub-agents, workflows, Monitor, traces, project context and MCP.