Skip to content

docs(factories): add "The platform behind a factory" section - #568

Merged
hongyi-chen merged 1 commit into
hyc/factory-launchfrom
oz/factories-platform-section
Aug 18, 2026
Merged

docs(factories): add "The platform behind a factory" section#568
hongyi-chen merged 1 commit into
hyc/factory-launchfrom
oz/factories-platform-section

Conversation

@hongyi-chen

Copy link
Copy Markdown
Collaborator

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:
    • What carries over from cloud agents: runs + session sharing, environments/runners/self-hosted workers, harnesses/secrets/MCP servers, and platform credits.
    • What the factory layer adds: foreman + roles, work items, definitions as code, default automations, and the Scorer/benchmark/Self-improvement loop.
    • When to use a standalone cloud agent vs. a factory.
  • 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)

  • Link check across all 17 factories pages: 0 broken pages, 0 broken anchors.
  • style_lint --changed: clean (only informational glossary warnings for bolded UI labels).
  • npm run build passes.

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>
@cla-bot cla-bot Bot added the cla-signed label Aug 18, 2026
@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Building Building Preview Aug 18, 2026 3:00am

Request Review

Copy link
Copy Markdown
Collaborator Author

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

View run View conversation

@warp-agent-staging

Copy link
Copy Markdown
Contributor

Your Warp account is not a member of any team with access to this repository.

@hongyi-chen
hongyi-chen marked this pull request as ready for review August 18, 2026 03:02
@hongyi-chen
hongyi-chen merged commit 8558fe8 into hyc/factory-launch Aug 18, 2026
3 of 4 checks passed
@hongyi-chen
hongyi-chen deleted the oz/factories-platform-section branch August 18, 2026 03:02
@oz-for-oss

oz-for-oss Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@hongyi-chen

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 /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant