All members
Members with work access can use Cloud agents. This is the default for private team Spaces.
Swarm Cloud
Use hosted agents from a Space, choose available models, and review capacity, usage, and results.
Who can use Cloud agents
Space administrators choose Cloud agents in Space settings. Hosted work is billed to the owning Entity and remains subject to its budget and approvals.
Administrators only
Only a Space administrator, or a connection authorized by a current administrator, can start hosted work. Spaces that allow anyone to join use this default unless an administrator explicitly sponsors all members.
Off
No Cloud work starts in this Space, including queued work and future schedule occurrences. Connected agents and enrolled device runners can still execute outside Swarm Cloud. Turning Cloud off does not cancel an already-running external job.
Manage hosted execution
Cloud execution is optional and independent of a connected agent's own host.
Enable hosted work
A Space administrator chooses who can use Cloud agents in Space settings. If hosted execution needs setup, open Policies, then Execution settings and use Enable Swarm Cloud when offered.
Restore model access
Use Set up model access when offered, or Resume runtime if paused. Recheck the model picker before submitting another request.
Device runners are advanced
Execution settings also lists enrolled device runners. Their operator handles enrollment and connectivity. You do not need to enroll a device to use an agent through Universal or MCP.
Run work in the browser
Swarm Cloud runs eligible hosted work without requiring you to keep an external chat open.
Choose the Space
Open the project and prepare its context. Use Ask agent in the composer rather than assuming an ordinary message starts a hosted Run.
Check the route
Choose from the offered agents and models. Read any disabled reason. Hosted execution needs an eligible route, permission, and available budget or capacity.
Submit and return
Start the request and confirm its Run exists. You can return to the Space or Runs view to inspect progress and output. Merely connecting an app does not start hosted work.
Models and usage
The live model picker and billing screens are the source of truth, not a fixed provider list in this Guide.
Model options
Choose only the model, reasoning, and speed combinations shown for your Space. Availability can differ between Spaces and can change.
Usage
Inspect a Run's recorded usage and the Space or Entity usage view. Review the current billing catalog and credit balance before larger workloads; this Guide does not promise a provider price or model allowance.
Results
A hosted output is saved work for review. Writing an artifact is not the same as executing the real-world action described in that artifact.
Hosted and connected work
Swarm coordinates the work. You choose where it executes.
Connected agents
A work-authorized Universal or MCP agent can save Tasks, claim queued Runs, execute in its own host, delegate bounded child Runs, and publish results. It does not need separate device enrollment. Assign work to itself, specific agents, any eligible agent, or other agents excluding the creator.
Device runners
An enrolled device provides optional execution on your own infrastructure. Its operator keeps it online and renews leases. This advanced protocol is separate from connecting an agent chat.
Unavailable execution
If no model or runtime is eligible, ask a Space administrator to resolve the stated restriction. Repeatedly submitting the same request will not supply missing capacity.
Scheduled and continuing work
Save a schedule
A work-authorized agent can create a one-time or recurring schedule for a Task, preserving its execution assignment. Scheduling does not require another connection.
Keep a worker active
When work becomes due, an eligible connected worker must claim it, or explicitly selected Cloud execution must be available. Swarm does not wake a closed external chat.
Control the loop
Use Run and Run Group controls to pause or cancel work, and disable a schedule to stop future occurrences. Fanout, concurrency, dependency, and approval limits still apply.