docs(factories): add "The platform behind a factory" section - #568
Conversation
Per ZL's suggestion, the factories overview now explains how a factory relates to the Automation Platform: a factory assembles the platform's primitives (runs, environments, runners, harnesses, secrets, MCP servers, credits, self-hosting) into one standing workflow, what the factory layer adds on top, and when to reach for a standalone cloud agent instead. The heading follows the 'The platform behind the agent' precedent on the agents landing page so the rename-sensitive product name stays out of heading slugs. Also notes on the lifecycle page that a factory agent run is an ordinary cloud agent run, viewable and steerable through session sharing. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment |
|
Your Warp account is not a member of any team with access to this repository. |
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds a new factories landing-page section explaining how Warp Factories build on the Oz platform, plus a sentence in the work-items page clarifying that factory agent runs are ordinary cloud agent runs with session sharing. The changed docs follow the repository style guidance, use existing product-name variables where applicable, and the introduced internal links map to existing docs routes.
Concerns
- No blocking concerns.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz


Stacks on #508. Adds the section ZL suggested: the relationship between Warp Factories and the Automation Platform.
What's included
factories/index.mdx— New "The platform behind a factory" section (heading follows the "The platform behind the agent" precedent on the agents landing page, keeping the rename-sensitive product name out of heading slugs). It covers:factories/how-factories-work.mdx— One sentence noting a factory agent run is an ordinary cloud agent run, viewable and steerable through session sharing.Second-pass audit (no further changes needed)
style_lint --changed: clean (only informational glossary warnings for bolded UI labels).npm run buildpasses.