The next chapter of Orchestro.
Updated Read as Markdown ↗
Orchestro began with a straightforward idea: help people and coding agents turn product ideas into working software. Agent Factory takes that idea further.
The focus now includes understanding a product as it exists, deciding what is worth improving and checking whether the work actually helped.
What changes here
Agent Factory is the new identity and direction of this website. The old landing page, screenshots and installation pitch have been replaced by the Factory product explanation and documentation.
What happens to an existing installation?
Your existing Orchestro MCP installation is a separate project. This website replacement does not change its code, data or configuration. Keep using the legacy repository for the documentation corresponding to that package.
The previous npx @orchestro/init command belongs to Orchestro. It does not install Agent Factory.
Why do commands say “northstar”?
The current Factory repository uses northstar as its package command. factoryctl remains a compatibility alias. Agent Factory is the public product name; the documentation uses the actual executable names so examples match the code.
Make a fresh connection
Factory onboarding starts from your project and its current evidence. There is no automatic migration of Orchestro tasks, memory or MCP configuration advertised at this stage.
Read the Factory quickstart