Copilot Agent Mode vs Coding Agent: What's the Difference?

Copilot agent mode works inside your editor, on your machine, while you watch. You give it a task in chat, and it edits files and runs commands in your local project in real time. The Copilot coding agent, now called Copilot cloud agent, works in the background in a cloud environment on GitHub. You hand it a task or an issue, and it researches, plans and codes on a branch, then can open a pull request for you to review. Short version: agent mode is a pair programmer at your desk, and cloud agent is a teammate you delegate to.

Is the Copilot coding agent now called cloud agent?

Yes. GitHub's April 1, 2026 changelog introduces "Copilot cloud agent (formerly known as Copilot coding agent)". The same update says it is no longer limited to pull request workflows. It can now work on a branch without opening a pull request, write an implementation plan before it acts, and run deep research on your codebase.

Agent mode also looks different in new versions of VS Code. GitHub's docs still use the name "agent mode". In VS Code, you now select Agent from the agents dropdown in chat, next to built-in options like Ask and Plan. If a tutorial tells you to "switch to agent mode", that is the same thing.

Copilot agent mode vs cloud agent at a glance

What is Copilot agent mode?

GitHub sums it up as: "Give Copilot a task and let it work autonomously in your editor." Copilot decides which files to change, makes the edits and runs commands as needed. Unlike a plain chat answer, it keeps going until the goal is reached or it needs input from you.

Agent mode is available in Visual Studio Code, Visual Studio, JetBrains IDEs, Xcode and Eclipse. In Visual Studio you need version 17.14 or later.

How to use agent mode in VS Code

1. Open the chat view. If it is hidden, select Open Chat from the Copilot Chat menu.
2. At the bottom of the chat view, select Agent in the agents dropdown.
3. Type your task and submit it.
4. Watch the edits stream into your editor. Approve terminal commands when asked.
5. Review the changes, ask for fixes, or run a code review.

By default, you approve commands before they run. Your admin or your editor settings can allow some commands to run automatically.

Good jobs for agent mode:

• Refactoring code you are actively working on
• Fixing a failing test while you watch
• Exploring an unfamiliar codebase with live feedback
• Anything where you want to steer each step

What is Copilot cloud agent?

GitHub says cloud agent "can research a repository, plan changes, and implement them in the background." It edits files and runs tests and linters in a cloud environment, not your local IDE. You do not need to keep your editor open while it works.

How to start a cloud agent task

1. From an issue: open an issue on GitHub.com and assign it to Copilot in the Assignees sidebar. Copilot starts a session and begins work on a pull request.
2. From the agents tab: go to github.com/copilot/agents, pick a repository, type a prompt and press Enter.
3. From VS Code: use /delegate to hand a well-scoped task to a cloud agent. You can also manage cloud agent sessions from your IDE.

To check what it did, open the session log with View session from the pull request.

Good jobs for cloud agent:

• Well-defined issues from your backlog
• Adding tests to an untested module
• Small features and bug fixes with clear acceptance criteria
• Research questions about the codebase you want answered while you do other work

Cloud agent limits to know

• It can only change the repository you picked when you started the task.
• It works on one branch at a time and opens one pull request per task.
• Each session can run for up to 59 minutes.
• It only works with repositories hosted on GitHub.

Which plans include agent mode and cloud agent?

GitHub's docs say Copilot cloud agent is enabled by default for Copilot Pro, Pro+ and Max. For Copilot Business and Copilot Enterprise, it is disabled by default, and an administrator must turn it on through the Copilot cloud agent policy.

The agent mode docs list supported IDEs but do not single out plans. Check GitHub's plan page for your account.

How much do agent mode and cloud agent cost?

Billing changed in 2026. GitHub moved all Copilot plans to usage-based billing on June 1, 2026. Usage now consumes GitHub AI Credits, priced by tokens at each model's rates. Code completions and next edit suggestions do not use AI Credits.

The legacy row only applies to Copilot Pro and Pro+ subscribers on an existing annual plan who stayed on request-based billing after June 1, 2026. For your exact allowance, see GitHub's billing docs linked below.

When should you use agent mode vs cloud agent?

Use agent mode when:

• You want to see and steer every change.
• The task touches code you are editing right now.
• You need fast back-and-forth.

Use cloud agent when:

• The task is clear enough to write as an issue.
• You want to work on something else while it runs.
• You want the result as a reviewable branch or pull request.

Many teams use both. Plan and prototype with agent mode, then delegate the follow-up tasks to cloud agent.

Do custom agents work with both?

Yes. A custom agent profile in .github/agents/NAME.agent.md can be selected in your IDE's agents dropdown and in cloud agent on GitHub.com. Some properties only apply in one place. For example, mcp-servers is ignored by IDE custom agents, and handoffs is ignored on GitHub.com. GitHub also notes that using a custom agent directly in chat is different from delegating a task to cloud agent.

Frequently asked questions

Is Copilot coding agent the same as Copilot cloud agent? Yes. GitHub renamed Copilot coding agent to Copilot cloud agent in April 2026 and added planning, research and branch-only work at the same time.

Does agent mode run in the cloud? No. Agent mode works in your editor on your local project. Changes land in your working files, and you approve terminal commands by default.

Can I start a cloud agent task from VS Code? Yes. VS Code supports the Copilot cloud agent. Use /delegate to continue a well-scoped task with a cloud agent, and manage cloud sessions from the IDE.

Why can't I use cloud agent on my work account? On Copilot Business and Copilot Enterprise, cloud agent is off by default. An administrator has to enable the Copilot cloud agent policy first.

How long can a cloud agent session run? Each Copilot cloud agent session has a maximum execution time of 59 minutes.

Does cloud agent always open a pull request? No. Since the April 2026 update, it can work on a branch without creating a pull request. You decide later whether to open one.

Keep learning

• Ready to give either agent a specialty? Follow How to build a custom GitHub Copilot agent (step by step).
• Connect both agents to outside tools with How to connect MCP servers to GitHub Copilot.
• Practice with real projects in the free course GitHub Copilot Agents from Scratch.

Sources

• Research, plan, and code with Copilot cloud agent (GitHub Changelog, April 1, 2026)
• Using agent mode in your IDE (GitHub Docs)
• GitHub Copilot in IDEs (GitHub Docs)
• About Copilot cloud agent (GitHub Docs)
• Get started with Copilot agents on GitHub (GitHub Docs)
• Managing access to Copilot cloud agent (GitHub Docs)
• Custom agents configuration (GitHub Docs)
• About custom agents (GitHub Docs)
• Models and pricing for GitHub Copilot (GitHub Docs)
• Overview of request-based billing (legacy) (GitHub Docs)
• GitHub Copilot is moving to usage-based billing (GitHub Blog)
• Agent harnesses (VS Code Docs)