Skip to content

docs: add the Cloud Agents section - #154

Merged
ValeryAntopol merged 3 commits into
mainfrom
feat/cloud-agents-docs
Nov 19, 2026
Merged

ValeryAntopol merged 3 commits into
mainfrom
feat/cloud-agents-docs

Conversation

@ValeryAntopol

@ValeryAntopol ValeryAntopol commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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):

Page Mode
build/cloud_agents/overview: Cloud agents concepts Explanation
build/cloud_agents/get_started: Launch your first cloud agent Tutorial
build/cloud_agents/ai_providers: Connect an AI provider How-to
build/cloud_agents/secrets: Add a GitHub token and secrets How-to
build/cloud_agents/extensions: Add MCP servers, plugins, and skills How-to and reference
build/cloud_agents/presets: Create and edit presets How-to
build/cloud_agents/manage_agents: Work with a cloud agent How-to
build/cloud_agents/troubleshooting: Troubleshoot cloud agents Reference

Also: the section is added to sidebars.js (so it is in llms.txt), a Cloud agents row is added to the console sections table in build/overview, and one sentence is added to the Build llms.txt header.

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:

  • The overview opens with what cloud agents give you and describes the life of an agent in words. The state table and the preset references are gone from it.
  • Removed: the role message, the notes about an unconfirmed launch or message, the model text field, the tab list, and the description of the conversation contents.
  • Secrets: values are stored encrypted and deleted on removal. A fine-grained GitHub token does not reach organization repositories by default and needs Workflows to change workflow files.
  • Unpushed work is gone with the machine: said at the stop step and in the idle stop section.

How the facts were checked

  • UI labels, page layout, form fields, validation messages, states, delivery labels, and failure messages: read from the source code of the Cloud agents console UI that is about to ship. Not observed in a running console.
  • Behaviour that the console does not spell out: read from the source code of the Cloud agents service. This covers secret names becoming uppercase environment variables, 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 gate passes (typecheck and build, no broken links or anchors).

Not verified

  • That secret values are stored encrypted and deleted on removal, and that the machine has no SSH access and no static public IP address: stated by the product owner, not observed.
  • Control of agents through the API: the published OpenAPI document has no agent endpoints yet. Control through MCP: agent tools were seen on a connected Fluence MCP server, but the MCP pages of these docs do not list them.
  • The fine-grained token rules (resource owner, Workflows permission): written from knowledge of GitHub, not checked against the token form.
  • Nothing was observed live: no agent was launched, and no page was opened in the console. Hold the merge until the new Cloud agents UI is released and the pages are read against it.
  • A launch requires a repository in the UI code this was written from. If the release makes the repository optional, get_started, manage_agents, and troubleshooting need an edit.
  • The default idle time and the limit of agents alive at once are deployment settings. The pages name no number for them.
  • That the machine of an agent is charged to the account balance like other machines, and what exactly happens to an agent when the balance runs out.
  • Whether a private skills repository is cloned with the GitHub token.
  • That the Fluence MCP server works as an agent's MCP server with an API key in X-API-KEY (assembled from the MCP page of these docs and the form's own hint, not run).
  • The short reason codes in the Last turn column other than the four listed.

@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
fluence-dev-docs Ready Ready Preview Nov 18, 2026 8:14pm UTC

Request Review

@CLAassistant

CLAassistant commented Nov 18, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

- 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.
- 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
ValeryAntopol marked this pull request as ready for review November 19, 2026 05:24
@ValeryAntopol
ValeryAntopol enabled auto-merge (squash) November 19, 2026 05:24
@ValeryAntopol
ValeryAntopol merged commit f31c51f into main Nov 19, 2026
3 checks passed
@ValeryAntopol
ValeryAntopol deleted the feat/cloud-agents-docs branch November 19, 2026 10:50

This branch was successfully deployed

1 active deployment
Preview — 59c69ad0 Deployed Nov 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants