Skip to main content
Early Access. Commands and behavior can change between releases.
You need a GitHub repository and a GitHub Project board you can access.
1

Install and onboard

Install Architech, then start it in your repository:
In the session, type /onboard. Pick your board’s owner and project number, then review the proposed changes. Onboarding writes .architech/factory/factory.yaml in local mode and adds a pointer to CLAUDE.md. If you skip the board, it writes neither.
2

Check the configuration

Check the repository names, default branches, board and merge policy in the file.
Validation runs offline and checks the file’s shape only. It does not prove that a Cloud workspace can reach your repositories or board.
Read configuration before you map an existing board’s columns.
3

Try it locally

In Architech, run /sync to read your board. Ask the orchestrator to plan a small change, and review the plan before you dispatch it. For an issue that already has a plan, run /dispatch <issue-number>, then /status to follow it.Pick a first task small enough that you can review its diff and tests yourself. A local file does not turn on Cloud pickup.
4

Move to Cloud (optional)

You can stay local. To run stages on Mutagent Cloud, follow Cloud setup: sign in, add a model provider to your workspace and connect GitHub.Then preview and push the file from the repository root:
A real push sets mode: cloud. If the file has no framework pin, push adds the one for your installed release. In a normal Git checkout, push commits the changed file. --dry-run writes and commits nothing.
Check committed and any notices in the output. A successful push can still leave the file uncommitted, for example on a detached HEAD or when the commit fails.
Push reports linked, board and drift. It does not link repositories or bind the board. If push says the board is not bound, run architech factory board bind <factory> once, with the Factory ID that push returned.
5

Turn it on

When Cloud setup is done, enable the Factory with the ID that push returned:
Once it’s enabled, triggers start work. Put a small issue in any column except triage. Give it the pickup label (factory:pickup by default) and no hold label. Then watch its run and approve its plan.