Search phrases like remote coding agents or cursor cloud agents pricing mix two ideas: an agent that keeps working while your laptop sleeps, and an editor session you are still driving locally. They are not the same product shape.
Short answer: a remote coding agent runs in a vendor-hosted environment (usually a VM or container), clones your repository, installs dependencies, edits on a branch, runs tests or browsers when configured, and hands you a diff or pull request to review. You orchestrate from the web, Slack, GitHub, or an IDE, but the compute is theirs.
This page defines that category, walks through how a run works, contrasts remote versus local agents, and compares products whose official docs were read on 14 November 2026. For local inference and editor-side stacks, see Cursor local alternative. For agent runtimes and models you operate entirely inside your network—distinct from a vendor VM—see self-hosted AI coding agents. For credentials on unattended VMs, see AI coding agent credentials and API keys.
What counts as a remote coding agent
A remote coding agent is autonomous or semi-autonomous software development work that executes outside your local checkout. The vendor provisions an environment, loads your repo (or a snapshot you published), uses tools, shell, edits, browser, MCP, and stops when the task is done, blocked, or budget-limited.
It is still a coding agent: the artifact is source code and a git handoff, not a greenfield app builder canvas. App builders and company operators are adjacent; this page stays on repo-shaped automation.
Naming varies. Cursor's documentation calls them Cloud Agents (formerly Background Agents). GitHub uses Copilot in the cloud. OpenAI brands cloud work under Codex Cloud. Cognition sells Devin Cloud. Google Jules runs tasks in a VM. Anthropic runs cloud sessions for Claude Code on the web and via claude --cloud.
How a typical remote run works
Details differ by vendor, but the pattern is stable enough to evaluate any product:
Connect source control
An admin connects GitHub, GitLab, Bitbucket, or Azure DevOps (or you publish an environment snapshot). Cursor and Jules require read-write access for branches they push.
Configure the environment
Install scripts, secrets, network allowlists, and sometimes a Dockerfile or saved snapshot. Cursor documents agent-led setup, snapshots, and .cursor/environment.json (cursor.com/docs/cloud-agent, 2026-11-14).
Start a task
You prompt from cursor.com/agents, ChatGPT Cloud, GitHub, Slack, Linear, or the CLI. The agent plans, edits, and may run tests in the VM.
Review and promote
You inspect diffs, artifacts (screenshots/logs), and CI. Merge or request follow-ups. Production promotion should still ride your normal gates, see sandbox AI agents with production write access.
Remote versus local coding agents
| Dimension | Remote / cloud agent | Local agent (IDE or CLI) |
|---|---|---|
| Where compute runs | Vendor VM or container in their cloud | Your laptop or self-hosted machine |
| Laptop required | No, tasks continue offline from your perspective | Yes for local sessions unless you only queued a remote job |
| Secrets surface | Vendor dashboard secrets injected at VM start | Your shell, .env files, OS keychain, higher leak risk |
| Parallelism | Many concurrent VMs (plan-limited) | Usually one or few local sessions |
| Best fit | Long fixes, cross-repo work, PRs while you sleep | Tight feedback loops, air-gapped or strict LAN policy |
Products read on 2026-11-14, positioning and access
| Product | What the official docs say | Plan / price notes (same read date) |
|---|---|---|
| Cursor Cloud Agents | Isolated VMs; clone repo; branch + PR; MCP; artifacts and remote desktop (cursor.com/docs/cloud-agent) | Included on Premium and above, Teams, Enterprise, and legacy paid plans; Free and Plus excluded. Billing draws from plan usage; spend limit prompted at first use. Dollar tiers: see Cursor pricing (cursor.com/pricing read 2026-11-13). |
| OpenAI Codex Cloud | Cloud tasks with published environments, secrets, network controls; review diffs and open PRs (developers.openai.com/codex/cloud) | Access through ChatGPT sign-in and Cloud workflows; this page did not find a separate per-task dollar table on that URL, confirm in your ChatGPT plan before budgeting. |
| GitHub Copilot in the cloud | Researches repo, plans changes, creates PRs; start from GitHub.com, mobile, CLI, MCP (docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent) | Copilot Pro $10/mo includes cloud agent per docs.github.com/en/copilot/get-started/plans (read 2026-11-14); Pro+ $39, Max $100; AI credits pools documented on same page. |
| Google Jules | Clones repo in a VM; plan approval before edits; opens PR (jules.google/docs, read 2026-11-14) | Homepage jules.google lists free-tier limits 15 tasks/day and 3 concurrent; Jules in Pro 100 tasks/day and 15 concurrent; Jules in Ultra 300 tasks/day and 60 concurrent, dollar prices for Pro/Ultra were not on the homepage text fetched this run. |
| Devin (Cognition) | Autonomous engineer; cloud agents; PR-ready output (devin.ai marketing copy cited in cursor-competitors on this site) | devin.ai/pricing read 2026-11-14: Pro $20/mo includes cloud agents (Devin Cloud); Max $200/mo; Teams $80/mo + $40/mo per full dev seat; Enterprise quoted. |
| Claude Code cloud sessions | Runs on Anthropic infrastructure; clone/push via GitHub proxy; claude --cloud from CLI (code.claude.com/docs/en/claude-code-on-the-web) | Available on Pro, Max, Ultra, Team plans per same doc; counts toward plan usage alongside other Claude/Claude Code usage, see anthropic.com pricing for seats, not repeated here. |
Security and credentials on someone else's VM
A remote agent is still an agent with shell and network. Assume it can read any secret you inject and any file in the cloned repo unless you deny it.
Cursor documents team-scoped secrets in the Cloud Agents dashboard, egress allowlists, and security pages linked from cursor.com/docs/cloud-agent (read 2026-11-14). Claude Code cloud docs describe GitHub credentials staying encrypted server-side with a GitHub proxy (code.claude.com/docs, 2026-11-14). Jules' FAQ warns not to commit API keys and that code runs in a cloud VM with internet access (jules.google/docs/faq, 2026-11-14).
Operational checklist: inject secrets through the vendor UI, keep prod keys out of git, restrict outbound domains where offered, and scan diffs before merge. The developer-tool checklist lives in AI coding agent credentials and API keys.
Cost models, what actually moves the bill
Seat + usage pool. Cursor bundles Cloud Agents into higher editor tiers and bills model usage from the same pools described in Cursor pricing.
Copilot credits. GitHub documents monthly AI credit allowances per plan and charges beyond the pool (docs.github.com/en/copilot/get-started/plans, 2026-11-14).
Task throughput caps. Jules publishes tasks-per-day and concurrency on jules.google (read 2026-11-14), which cap parallelism even when dollar price is low.
Autonomous engineer quotas. Devin Pro/Max publish subscription prices on devin.ai/pricing (read 2026-11-14) plus API-priced extra usage on paid tiers, confirm current wording on that page before purchase.
None of these replace your own CI minutes, code review time, or incident cost when a bad merge ships.
How to choose
Match the handoff you want
Need a PR against your existing monorepo? Prefer products that clone from GitHub/GitLab with branch push. Need a greenfield artifact? An app builder may fit better, see best AI app builders.
Count unattended secrets
If the agent runs overnight, secrets injection and egress policy matter more than model brand. Read the security doc for your vendor before the first run.
Separate remote coding from operating a company
Remote agents accelerate engineering; they do not by themselves operate marketing, support, and finance on a schedule.
Keep local and remote distinct
Teams with strict LAN policies may still forbid cloud VMs even when local Cursor sessions are allowed, compare against Cursor local alternative.
Where Empyre fits
Empyre is not a remote coding-agent substitute for your repository. You describe a company in plain language; Empyre staffs eight executives that build the product, publish it to its own address, and keep scheduled work running, marketing, support, finance gates, and releases, after launch. Customer payments route to your connected Stripe account per published empyre.dev pricing.
A remote coding agent can still be part of your engineering workflow while Empyre operates the business you asked it to run. The categories overlap at "agents write code" but not at "who owns post-launch operations."
Common questions
Are Cursor Cloud Agents the same as remote coding agents?
Yes in category terms: they run in isolated cloud VMs, clone your repo, and push branches (cursor.com/docs/cloud-agent, 2026-11-14). They are not included on Free or Plus plans.
Does a remote agent replace code review?
No. Vendors expect you to review diffs, artifacts, and CI before merge. Treat unattended runs as untrusted until a human or policy gate approves.
Is this page about Empyre's agents?
Empyre's executives run as a scheduled company operator, not as a checkout of your personal GitHub repo on demand. Use this page to buy engineering automation; use AI platforms that generate a full business to sort full-company products.
Try Starter free for 3 days
Describe a business in plain words and watch eight AI agents build and deploy it. Starter is free for the first 3 days; a card starts the trial.
Related
Last updated 2026-11-21. Competitor descriptions reflect each product's publicly documented capabilities at that date; they change often, so check the source before relying on a detail.