Playbooks · Coding tasks
Hand a task to a Cline cloud agent
Written November 5, 2026
Cline Cloud Agents run a task in the cloud and hand back a branch, but rules, skills, and MCP stay behind. What loads, what drops, and how to brief it.
What a cloud agent is
Cline Cloud Agents run Cline from the browser, with no IDE, CLI, or app to install. Give it a task on one of your GitHub repos and it works in its own secure cloud sandbox, writing code and running commands until the job is done, then hands the work back as a branch and pull request. The agent keeps working in the cloud when the tab closes, so several tasks can run at once and be followed from any device, including a phone.
How to hand a task
- Give it a task on one of your GitHub repos, from the browser. Nothing to install.
- Choose a model when starting; switch mid-session if needed. Providers: ClineFree for free models, ClinePass for open-weight models on subscription, or Cline usage-billing for pay-as-you-go access with credits.
- Steer with Plan and Act modes, approvals or auto-approve, images as context, and follow-ups.
- Review the branch: each task works on its own
cline/branch and never commits directly to the default branch. The agent commits and pushes as it goes, so progress is on GitHub before the task finishes.
What does not load
Rules, skills, MCP servers, and connectors are not loaded in cloud sessions. That is the documented gap, and it changes how a task must be briefed: put the instructions the task needs in the task text itself, and check whether its dependencies are available in the sandbox, because nothing from local Cline carries over. GitHub access in a session is limited to the repository picked for that session.
Session limits
Up to 10 cloud agent sessions can run at once, and up to 50 new sessions can start per day. If the cloud is at capacity, Cline asks you to try again shortly. A session that sits idle for 15 minutes pauses its sandbox; opening the session again picks up where it left off, with the workspace intact.
No comparison is reported here
A local run and a cloud run of the same task would show how much the missing rules, skills, and MCP change the result. No such comparison is reported here, so this page makes no claim about which route does a task better, faster, or cheaper. Until a comparison exists, treat the cloud session as a different setup from local Cline, not as the same setup in another place.
Limits
- This page follows the Cloud Agents docs. Cloud Agents are new, and the list of what does not carry over may change; the docs page is the place to check.
- No Cline account or cloud access was used for this page, so no run — local or cloud — is described here.
Related playbooks
- Antigravity's remote agents run in Google's cloud
- Cursor builds live apps from cloud agents
- Claude Code 2.1.328 makes auto mode the cloud default
- A malicious MCP server probed cloud credentials
Sources
- Cline Cloud Agents — what cloud agents are, the providers, the session limits, and what does not load.
Back to: Coding playbooks. Also: Run three independent lines of research at the same time in Claude Code, then combine the short summaries · Have one agent write the code and a second agent check it in the background.