Version 1.107 is now available! Read about the new features and fixes from November.
Dismiss this update
GitHub Copilot coding agent is a GitHub-hosted, autonomous AI developer that works independently in the background to complete development tasks. To invoke the coding agent, assign a GitHub issue to Copilot or delegate a task from chat, and the agent will work autonomously to implement features, fix bugs, and make changes across your repository using its own isolated development environment.
This is different from using agents in VS Code, which provide interactive development within the editor and requires your active participation during the coding session.

The Copilot coding agent workflow:
@copilot, delegate a task from VS Code chat, or use TODO code actionsBefore you can use Copilot coding agent, you need:
Ensure you are signed into the GitHub Pull Request extension with the correct GitHub account.

Optional: Enable the experimental setting githubPullRequests.codingAgent.uiIntegration to show a Delegate to coding agent button in Copilot Chat for easier task delegation.
You can also manage coding agent sessions from a dedicated chat editor and view a Chat Sessions view by enabling the experimental setting chat.agentSessionsViewLocation.
If you don't have Copilot access yet, you can sign up for the Copilot Free plan to get a monthly limit of interactions.
You can trigger Copilot coding agent by assigning a GitHub issue to Copilot, similar to how you assign an issue to a team member. Copilot coding agent automatically analyzes the issue and starts working on it.
In the GitHub Pull Requests view, navigate to the Issues section
Find the issue you want to assign to Copilot
Right-click the issue and select Assign to Copilot or select Assign and then select @copilot
You can also assign issues to @copilot directly on GitHub.com. The coding agent will work the same way, creating a pull request that you can then review in VS Code or on GitHub.
The agent will begin working on the issue in the background
Open the Chat view in VS Code (⌃⌘I (Windows, Linux Ctrl+Alt+I))

You can also hand off work to Copilot coding agent directly from your chat conversation. Instead of having the agent implement changes immediately in your editor, you can delegate the task to the coding agent to work on it autonomously in the background.
Open the Chat view in VS Code (⌃⌘I (Windows, Linux Ctrl+Alt+I))
Have a conversation about the feature or change you want to implement
When ready, delegate to the agent by using one of these methods:
Use the delegate button (Experimental)
Enable the experimental setting githubPullRequests.codingAgent.uiIntegration to show a Delegate to coding agent button in the Chat view for repositories that have the agent enabled. Select this button to hand off your current chat context to the coding agent.
When you delegate a task, additional context including file references are forwarded to the coding agent, enabling you to precisely plan out a task for the coding agent to complete. A new chat editor opens with the coding agent's progress shown in real-time.
Use the #copilotCodingAgent tool
You can also reference the #copilotCodingAgent tool directly in your prompt to ask Copilot to continue a local change in the background. This tool automatically pushes pending changes to a remote branch and initiates a coding agent session:

The agent will create a pull request and begin implementing the discussed changes. When you start a coding agent session (via #copilotCodingAgent or with the Delegate to coding agent action), the pull request is rendered as a card in the Chat view.

Comments starting with TODO in your code now show a Code Action to quickly initiate a coding agent session. This provides a convenient way to delegate specific tasks directly from your code.
The TODO keyword is configurable via the githubIssues.createIssueTriggers setting. You can customize which comment keywords trigger the coding agent code action.
Navigate to a TODO comment in your code
Look for the light bulb icon or use ⌘. (Windows, Linux Ctrl+.) to open the Quick Fix menu
Select Delegate to coding agent from the available code actions

The coding agent will analyze the TODO comment and implement the requested changes in a new pull request
When you assign work to Copilot coding agent, it follows a specific workflow that may differ from your expectations:
Initial pull request creation: The agent immediately creates a pull request with an initial empty commit. This establishes the workspace and branch where all changes will be made.
Background processing: The coding agent works in GitHub's cloud infrastructure (GitHub Actions environment), not on your local machine. This means:
Incremental updates: After the initial commit, the agent will push additional commits with the actual code changes as it develops the solution.
If you see an initial commit with no changes, this is expected behavior. The agent will continue to push actual code changes in subsequent commits as it works on your task.
The GitHub Pull Requests extension provides a dedicated Copilot on My Behalf section that shows:

You can also monitor work that you assigned to @copilot through GitHub.com - all active sessions and pull requests will appear in this section regardless of where you initiated them.
In the Pull Requests view, find your agent's work under Copilot on My Behalf
Select View Session to see a detailed log of everything the agent did:

You can manage coding agent sessions from a dedicated chat editor that enables you to:
Enable the experimental setting chat.agentSessionsViewLocation to try this feature:
When set to view, you'll see a Chat Sessions view in the VS Code Side Bar for managing local and coding agent sessions. The view now includes rich descriptions with detailed context to help you quickly find relevant information.

When set to showChatsMenu, coding agent sessions appear alongside local chat history

Pull requests created by the coding agent are also rendered as cards in the Chat view when you start a session, providing better visual integration.
The delegation experience from VS Code to GitHub coding agent has been significantly enhanced in recent updates:
These improvements make it easier to precisely plan out tasks for the coding agent and monitor their progress without leaving VS Code.
If you need to stop the agent, you can stay in VS Code and use the Cancel coding agent button on the PR overview page.
You can also cancel a session from GitHub.com:
After the Copilot coding agent has analyzed your code and determined the changes that are needed to accomplish the task, it performs the following steps:

You can guide the agent's work through pull request comments. Make sure to tag @copilot in your comments so the agent will respond:
Request changes: Leave specific feedback about what needs to be modified
@copilot Please update the login form to include password strength validation
Request improvements: Ask for additional features or refinements
@copilot Can you add error handling for network timeouts?
The agent will respond to your feedback, make the requested changes, and update the pull request.
When working with pull requests created by the coding agent, the #activePullRequest tool is automatically enabled for your chat session. This gives chat context about your PR, including what files were changed, who's assigned, and the state (draft or ready for review). You can then ask about this PR and iterate further on it in chat.
VS Code offers two autonomous coding experiences. While using agents in VS Code provides interactive development directly within the editor, the Copilot coding agent works independently on GitHub to implement features in the background.
| Feature | Copilot coding agent | Using agents |
|---|---|---|
| Where it runs | GitHub cloud | Your VS Code editor |
| Independence | Fully autonomous | Involves user interaction and iteration |
| Output | Creates pull requests | Edits files directly |
| Best for | Well-defined tasks, background work | Interactive development, immediate feedback |
Learn more about using agents in VS Code.
When Copilot coding agent starts working, it creates an initial empty commit to establish the pull request and working branch. This is expected behavior - the agent will push subsequent commits with actual code changes as it works in GitHub's cloud environment.
You can monitor progress through the session logs accessible from the pull request, the GitHub Pull Request extension's Copilot on My Behalf section, or the Chat Sessions view.
Copilot coding agent includes built-in security protections and operates within GitHub's security framework. For detailed information about security measures, permissions, and branch protection compatibility, see the GitHub Copilot coding agent security documentation.
For advanced scenarios, you can extend Copilot coding agent with Model Context Protocol (MCP) servers to give it access to:
Learn more about extending Copilot coding agent with MCP.
For detailed information about limitations, compatibility, and usage costs, see the GitHub Copilot Coding Agent documentation.