Run with your coding agent.
Updated Read as Markdown ↗
Factory brings the context and the working rules. Your coding CLI does the agent work.
Agent execution uses locally installed CLIs authenticated with your existing subscription. Factory does not add a model API billing layer or automatically fall back to a paid API key. Provider quotas and terms still apply.
Current compatibility
| Agent | Setup & context | Loop execution |
|---|---|---|
| Claude Code | Shared onboarding skill | Claude adapter |
| Codex | Shared onboarding skill | Codex adapter |
| Grok | Via a compatible skill host | Grok adapter; CLI required |
| Muse Spark (Muse CLI) | Mapping proposals + Product Advisor | No selectable repair worker adapter yet |
| Gemini CLI | Shared onboarding skill | No selectable worker adapter yet |
| Other agents | Can read the workflow instructions | Requires a supported adapter |
Muse Spark for mapping and advice
Factory uses the installed muse CLI to propose mapping content and run Product Advisor reviews. Muse Code is Meta’s terminal agent for Muse Spark. In the current Factory adapter set, Muse supports these review roles; it is not selectable as the autonomous repair worker.
npm run northstar -- product-advisor run --pack packs/my-app --agent museSee the full command reference for mapping, intake and execution tools.
One workflow across hosts
The project includes a provider-neutral onboarding skill at .agents/skills/onboard-project/SKILL.md. A host that does not discover skills can read that file directly and follow it.
Reading a skill is different from being a supported unattended worker. The existence of a new CLI or model does not automatically add a new Factory adapter.
Check your selected agent
npm run northstar -- preflight --agent codexFor a configured provider chain, check the actual project pack:
npm run northstar -- preflight --pack packs/my-appWhen a provider runs out of quota
A project can declare a provider chain. When a provider exhausts its subscription quota, Factory can hand the work to the next installed, configured provider. The handover is recorded with the issue. If no configured provider can work, the quota limit remains a visible stop.
The models still consume subscription usage. “No separate model API bill” does not mean zero tokens or unlimited capacity.
Your permission settings travel with the work
Provider choice does not expand what Factory is allowed to do. Keep the project’s scope, acceptance criteria and release boundaries explicit, whichever agent handles the task.