Document single-prompt Factory MCP onboarding - #585
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Add a copy-pasteable agent prompt that bootstraps Factory MCP installation and hands onboarding to the guidance published by the server. Update the feature summary, onboarding examples, and tool reference for factory creation. Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
fd49ca5 to
89a7d80
Compare
|
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 |
![warp-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR updates the Factory MCP documentation with agent-driven setup guidance, onboarding tool descriptions, and revised authentication guidance. The new flow is useful, but a few changed lines conflict with docs terminology and the linked API-key reference.
Concerns
- The central prompt uses
Warp Factoryfor an individual factory, which conflicts with the Warp Factories terminology rule and is repeated in the examples. - The API-key fallback introduces
Team API key, but the linked reference defines the supported key types as personal and agent API keys. - The new tool-reference rows capitalize
Factorywhere the docs style guide treats it as a lowercase common noun.
Verdict
Found: 0 critical, 3 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| 2. If it is not available, identify the coding environment and add `https://app.warp.dev/api/v1/mcp/factory` using that client's current MCP configuration mechanism. | ||
| 3. Open the browser-based Warp authorization flow, where you can log in or create a Warp account. | ||
| 4. Verify the Factory MCP tools are available. | ||
| 5. Use the onboarding guidance published by Factory MCP to create or join your first team conversationally, complete browser-based Stripe funding if required, and select repositories, factory agents, and optional integrations before creating the factory. |
There was a problem hiding this comment.
might just be some internal implementation details we don't need to expose
There was a problem hiding this comment.
instead of removing these entirely though, I added them to a new AgentOnly component that doesn't expose the text to human readers but will expose to agent readers who download the .md. That way the prompt can be really clean and this page can have the info the agent needs, but we don't need to make it messy.
Does that seem reasonable?
hongyi-chen
left a comment
hongyi-chen
left a comment
There was a problem hiding this comment.
thanks for putting this tgt! we can make it a bit more brief and abstract away some of the implementation details of the setup agent
2764a28 to
56f677d
Compare
2 participants
Summary
Adds a single copy-pasteable prompt to the existing Factory MCP page so a coding agent can install and authenticate Factory MCP using its own environment conventions, then hand off to the onboarding guidance published by the MCP server.
Related implementation:
Docs outline
create_factoryto mention repository, integration, and optional factory-agent selection.Verified from codebase
Items needing review
Validation
npm run build— passed.trunkwas unavailable locally, so the Trunk wrapper was not run./cc @harryalbert
Warp conversation
Co-Authored-By: Warp agent@warp.dev