Software Factory — you sign the plan and the PR merges itself
Updated 2026-10-17
Read https://www.ghosty.studio/en/docs/factory.md and tell me how to install the Ghosty Software Factory in my Teams workspace and how to ask for my first change.
The Software Factory is two agents, Arqui and Worker, that work your GitHub repository from a room. You write what you need the way you'd tell a person and sign once: the plan. They do the rest, and the PR lands on main by itself with automerge (on by default in every room) as soon as Arqui approves it and CI passes.
Nothing lands on trust: red CI means no merge, a plan that requires a preview doesn't merge without one, and a major dependency bump always waits for a person. If your team prefers to sign every PR, turn automerge off in the room; then every PR arrives with its risk, what to read first and how it looks.
Arqui and Worker
The flow is the same as always: plan → signature → build → CI → review → PR → production. Arqui does the plan and the review; Worker does the build. @plan, @build and @check still work as aliases.
Each one is a Studio agent you choose (engine, model and keys are changed in /app/agents). The same agent can be @ghosty in another room and Worker here: the part reaches it per turn. The usual setup is a strong model for Arqui (Opus) and a cheaper one for Worker (for example, DeepSeek Flash). An Arqui on a different engine than Worker reviews better, because it doesn't share its blind spots.
To research, Arqui launches 2 or 3 read-only helpers at once: they read the repo and search the web for what the industry does, with sources. Arqui writes the plan and the verdict itself. It is turned on per workspace, like Worker's helpers.
Arqui also runs a run's postmortem. Ask «@arqui what happened with #96?»: it reads the run's analysis (the same one as ) and proposes, as «Ask» cards, the guardrails that would have stopped it: the repo setup, a review rule, CI or a note in docs/agents/. It talks about the process, never about people. If a run was approved without meeting a criterion of its plan, it does this on its own, once, in the run's thread.
Install
- Teams → Settings → Apps → Software Factory (workspace owner only).
- Pick the repo and which Studio agent is Arqui and which is Worker. Connect your GitHub to sign.
- The factory room and its Tasks board are created. Every room with repos is a factory: you can bind more repos to other rooms.
- In
/factory, "Ready for agents" grades the repo and "Prepare repo" opens a single PR with what's missing: CI,AGENTS.md,CODEOWNERSand Dependabot. With GitHub Pro or Team (or a public repo), "Protect main" turns on the rule that nothing gets in without approval. The factory enforces the preview a run requires when merging; on the PR you'll see it as the informational check.
Ask for a change
- Arqui posts the plan card. Sign it with the button, with "✅" in the thread, or ask for changes with "cambios: …".
- Once signed, Worker builds with your GitHub and opens a draft PR. Its work box shows in the thread, under its avatar: working, asleep, starting, waiting for a slot or error.
- Arqui reviews it. If it passes, the platform takes the PR out of draft and posts the verdict card.
- With automerge on (default), the PR lands on main as soon as CI passes; if CI goes red, it goes back to Worker. With automerge off, you review and merge from the card or on GitHub. The request closes by itself when merged.
If the request requires the preview (the plan marks it, or it is a major dependency bump), Arqui can't approve without testing it and «Merge» is blocked until it's ready; the platform also sends it a real request (a POST with the browser's Origin). Details in .
Other ways in: assign a task to Arqui in Tasks, ghosty teams post <workspace>#<room> "@arqui …" from the terminal (), "What do you want to achieve?" in /factory (it splits it into a sprint of 3 to 8 tickets), "Suggest requests" and scheduled reviews in "Automatic". Any agent can propose a new request with a "Pedir" card; a person sends it with one click (agents never hand work to each other with an @-mention).
The verdict card
What you need to review the change, before or after the merge, without rebuilding it in your head:
- Risk. The platform marks it from what the PR touches, not from the agent's word: authentication, migrations, dependencies, public API,
.github/or more than 400 lines → high. Arqui can raise it for delicate logic, never lower it. - Read first. Up to five
file:lineswith the why, most delicate first. - Screenshots. If the repo has previews, the screen that changed on desktop and mobile.
- Preview. If the request requires it: ✓ tested, or what it's missing (building, missing variables, failed).
- Changes, CI and review: files and lines, CI status (verified on GitHub) and how many rounds it took with Arqui's review.
- Details: what Arqui said in its review, folded.
What's measured
In /factory, per room:
Next
- :
.ghosty/factory.mdand "@build con opus". - : what agents must know about your repo, in your repo.
- : compare agents and models on your own requests.