Coding & Git

Cloud agent

Also called cloud agents.

A cloud agent is an AI coding agent that runs on a computer the vendor hosts, instead of only on the machine in front of you.

Example

You assign a bug to a cloud agent. It works on a hosted computer, changes a branch, and opens a pull request for you to review. Your laptop does not have to stay open for that run.

Why it matters

GitHub's Copilot cloud agent can research a repository, make code changes on a branch, and create a pull request. It works in its own ephemeral development environment, powered by GitHub Actions. GitHub's docs say this is distinct from agent mode in an IDE, which edits files in your local environment. You can review the diff and iterate before a pull request is created, or ask for a pull request right away.

Cursor's docs say Cloud Agents run in isolated cloud environments and can build features, fix bugs, write tests, and open pull requests. Each task starts from a configured environment. xAI's Grok Bot teams docs say a Bot can delegate coding tasks to Cursor Cloud Agents on separate computers, under the Cloud Agent controls you already have. A team switch on the Grok Bot page allows or blocks that delegation. The docs say the switch is on by default, and admins can turn spawning off.

How it shows up on bot.ski

On bot.ski, the Coding agent glossary page already names GitHub's cloud agent as one kind of coding agent. The blog note about handing coding to Cursor discusses Cursor cloud agents as part of that handoff. This page is the definition. bot.ski does not start a cloud agent, and opening this page does not open a pull request.

Common confusion

A cloud agent is not the Grok Bot cloud computer. That computer is one persistent machine shared by the Bots on an account. GitHub's Copilot cloud agent and Cursor's Cloud Agents are different products that both use this name. Opening a pull request is not a deploy.

Sources

Updated October 3, 2026.

Cookie preferences