Repository navigation
docs: add the Cloud Agents section - #154
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Overview: open with what cloud agents give you (managed agent, isolated machine, reproducible setup, control from the console, MCP, or the API). Describe the life of an agent in words instead of a state table, and drop the preset references. - Secrets: say that values are stored encrypted and deleted on removal, and that a fine-grained GitHub token does not reach organization repositories by default. - Remove the role message, the unconfirmed launch and message notes, the model text field, the tab list, and the description of the conversation contents.
ValeryAntopol
force-pushed
the
feat/cloud-agents-docs
branch
from
November 18, 2026 17:58
77a8243 to
dd8f77d
Compare
- Overview: the machine is released on stop or idle, not when the work is done. Say that the machine also runs while the agent is idle, and that unpushed work is gone with the machine. - Get started: repeat the unpushed work warning at the stop step. - Secrets: a fine-grained token needs Workflows, not Actions, to change workflow files. Move the name example next to the reserved prefixes it belongs to.
ValeryAntopol
marked this pull request as ready for review
November 19, 2026 05:24
ValeryAntopol
enabled auto-merge (squash)
November 19, 2026 05:24
justprosh
approved these changes
Nov 19, 2026
This branch was successfully deployed
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.
What changed
A new Cloud Agents section in the Build sidebar, written from the console's point of view (pages, buttons, fields, and wording as on screen):
build/cloud_agents/overview: Cloud agents conceptsbuild/cloud_agents/get_started: Launch your first cloud agentbuild/cloud_agents/ai_providers: Connect an AI providerbuild/cloud_agents/secrets: Add a GitHub token and secretsbuild/cloud_agents/extensions: Add MCP servers, plugins, and skillsbuild/cloud_agents/presets: Create and edit presetsbuild/cloud_agents/manage_agents: Work with a cloud agentbuild/cloud_agents/troubleshooting: Troubleshoot cloud agentsAlso: the section is added to
sidebars.js(so it is inllms.txt), a Cloud agents row is added to the console sections table inbuild/overview, and one sentence is added to the Buildllms.txtheader.The overview says that agents can also be controlled through Fluence MCP and through the API. The pages that describe how are not part of this PR.
Later edits on this branch:
How the facts were checked
GH_TOKEN, reserved variable names, the two MCP headers, plugin package formats and limits, plugin order, the 6 hour turn limit, and refusal of a launch when a named secret is missing.npm run gatepasses (typecheck and build, no broken links or anchors).Not verified
get_started,manage_agents, andtroubleshootingneed an edit.X-API-KEY(assembled from the MCP page of these docs and the form's own hint, not run).