docs(m103): template-only install + two-tier template catalogue#115
Merged
Conversation
Fleet install is now template-only (install --template <id>); the local-directory install --from path is removed (fleet update --from live-edit stays). Reframe the install page, CLI reference, quickstart, authoring, tools, webhooks, credentials, troubleshooting, running, overview, and workspace pages around installing a pre-onboarded template from the workspace gallery; authoring routes through onboarding (dashboard/API). Add a changelog Update for the two-tier template catalogue (Breaking: install surface, removed bundle/snapshot endpoints) and the gallery description + credential-reason copy. Update the UZ-BUNDLE-002 message and the Fleet Bundle error-codes intro. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
- Sharing: clone → onboard → install --template, then iterate with fleet update --from (the old copy ran fleet update on a fresh machine with no fleet). - UZ-BUNDLE-005: 'Snapshot storage' → 'Template object storage' (matches the onboarding model). - Roadmap Note: 'first-party catalogue' → 'platform catalogue' (consistency). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Aligns the docs with M103 (two-tier Fleet template catalog).
What changed
agentsfleet install --template <id>is the install path;install --from <path>(local-directory install) is removed.fleet update --from(live-edit of an installed fleet) is unchanged. Authoring routes through onboarding (dashboard/API) then install by id.<Update>for the two-tier catalogue (Breaking: install surface + removed bundle/snapshot endpoints) and the gallery description + credential-reason copy.Pairs with the agentsfleet PR for M103.
🤖 Generated with Claude Code
Greptile Summary
Broad documentation alignment for M103: the install surface is now template-only (
agentsfleet install --template <id>), local-directory installs are removed, and a two-tier template catalogue (platform + workspace) is introduced. ~14 pages and the error-code reference are updated to reflect the new onboard-then-install flow and thefleet update --frompath for iterating on running fleets.--fromreferences from the install path across CLI reference, quickstart, authoring, tools, webhooks, credentials, troubleshooting, and overview pages.GET /v1/workspaces/{workspace_id}/fleet-templatesandPOST /v1/admin/fleet-templates/POST /v1/workspaces/{workspace_id}/fleet-templatesonboarding endpoints.<Update>entry documenting the breaking install-surface change and removed bundle/snapshot endpoints.Confidence Score: 4/5
Safe to merge with one correction in cli/agentsfleet.mdx before it ships.
The
agentsfleet templatessection incli/agentsfleet.mdxstill says "the same gallery the dashboard shows," but the PR explicitly adds that the dashboard now unions the platform catalogue with workspace-tier templates whileagentsfleet templatesonly hits the platform-only endpoint. A user who onboards workspace templates and looks for them via the CLI will find the reference doc wrong. All other pages update cleanly and consistently.cli/agentsfleet.mdx — the
agentsfleet templatescommand description needs the "same gallery as the dashboard" claim corrected and the "first-party" terminology updated to "platform".Important Files Changed
install --fromfrom the overview table and updates theinstall --templatedescription, but theagentsfleet templatessection still says "the same gallery the dashboard shows" (now inaccurate since the dashboard includes workspace templates) and retains stale "first-party" terminology.#install-from-the-cataloguesection preserved.GET /v1/fleets/bundlesnote and dashboard distinction are accurately distinguished.fleet updatefrontmatter rejection. Network allowlist section still tells users to "re-install" rather than usefleet update.UZ-BUNDLE-005now correctly references "Template object storage" instead of "Snapshot storage".fleet updateinstead ofinstall --from; example command is concrete and accurate.install --template <id>and template resolution. Card text updated to remove local-bundle mention.fleet updatepath mentioned for authoring workflow.install --templateinstead ofinstall --from; accurate and consistent.fleet update --frominstead ofinstall --from.install --fromtoinstall --template; accurate.install --fromtoinstall --template; accurate.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Author SKILL.md + TRIGGER.md] --> B{Onboarding path} B -->|Platform tier| C["POST /v1/admin/fleet-templates\n(platform:template:write scope)"] B -->|Workspace tier| D["POST /v1/workspaces/{ws}/fleet-templates\n(template:write scope)"] C --> E[(Platform catalogue)] D --> F[(Workspace gallery)] E --> G[agentsfleet templates / Dashboard gallery] F --> G G --> H["agentsfleet install --template <id>"] H --> I[Fleet created in workspace] I --> J["agentsfleet fleet update <fleet_id> --from <path>"] J -->|Re-parses + PATCHes live fleet| I%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% flowchart TD A[Author SKILL.md + TRIGGER.md] --> B{Onboarding path} B -->|Platform tier| C["POST /v1/admin/fleet-templates\n(platform:template:write scope)"] B -->|Workspace tier| D["POST /v1/workspaces/{ws}/fleet-templates\n(template:write scope)"] C --> E[(Platform catalogue)] D --> F[(Workspace gallery)] E --> G[agentsfleet templates / Dashboard gallery] F --> G G --> H["agentsfleet install --template <id>"] H --> I[Fleet created in workspace] I --> J["agentsfleet fleet update <fleet_id> --from <path>"] J -->|Re-parses + PATCHes live fleet| IReviews (2): Last reviewed commit: "docs(m103): address greptile review on #..." | Re-trigger Greptile