GitHub Copilot Cloud Agent in JetBrains: How to Use
To use the GitHub Copilot cloud agent in JetBrains IDEs, you enable the agent through the Copilot tool window, then submit tasks that the agent works on asynchronously in the cloud—reviewing code, running commands, and proposing changes that you can accept or reject. This article explains the setup, workflow, and practical tips for getting the most out of it.
What Is the GitHub Copilot Cloud Agent?
The cloud agent is a feature within GitHub Copilot that moves some AI assistance from your local machine to GitHub’s servers. Unlike the inline completions that appear as you type, the agent can handle broader, multi-step tasks: it can read your repository, run tests, inspect logs, and then present a plan or a set of code changes. In JetBrains IDEs (like IntelliJ IDEA, PyCharm, or WebStorm), the agent appears as a separate panel, often labeled Copilot Agent or Cloud Agent, depending on your version.
This is different from the classic Copilot chat, which is primarily a conversational interface. The agent is designed to work autonomously on a task you describe, using tools like file reading, terminal commands, and even web search (when enabled). It is especially useful for refactoring, fixing failing tests, or implementing a feature that spans multiple files.
Prerequisites and Setup
Before you can use the cloud agent, you need:
- A GitHub Copilot subscription (Pro, Business, or Enterprise) that includes the agent feature. As of 2025, the cloud agent is available to all Copilot paid tiers, but check your plan’s documentation.
- JetBrains IDE version 2024.3 or later (the agent requires recent IDE updates to support the protocol).
- The GitHub Copilot plugin installed and signed in with your GitHub account.
- An active internet connection; the agent runs in the cloud, so your machine must be able to reach GitHub’s servers.
To enable the agent, open the Copilot tool window (usually from the right sidebar). If you see a tab called Agent, click it. If not, go to Settings > Tools > GitHub Copilot and look for an option like “Enable Cloud Agent.” After enabling, you may need to restart the IDE.
How to Use the Cloud Agent: Step-by-Step
- Open the Agent panel: Click the Copilot icon in the right gutter, then select the Agent tab.
- Describe your task: In the input box, type a clear, specific instruction. For example: “Refactor the `UserService` class to use constructor injection instead of the service locator pattern.”
- Submit the task: Press Enter or click the send button. The agent will start working in the cloud. You’ll see a progress indicator and a stream of actions (e.g., “Reading file: src/main/java/UserService.java”).
- Review the plan: The agent may first present a plan or a list of steps it will take. You can approve it or ask for modifications before it proceeds.
- Monitor the work: The agent will edit files, run commands (like `mvn test` or `npm test`), and report results. You can interrupt it at any time with the “Stop” button.
- Review changes: When done, the agent shows a diff of all changes it made. You can accept all, reject all, or go through each change individually using the IDE’s diff viewer.
- Run tests yourself: Even if the agent says tests pass, it’s good practice to run the full test suite locally to confirm.
What the Agent Can Do (and What It Can’t)
The cloud agent is powerful but has limits. It can:
- Read and understand files across your project.
- Edit multiple files and create new ones.
- Run shell commands (like build tools, test runners, linters) and interpret their output.
- Search the web for documentation or error messages (if enabled in your Copilot settings).
- Propose a step-by-step plan for complex tasks.
It cannot:
- Access your local environment beyond what the IDE exposes (it runs in the cloud, so it can’t see your local files unless they are committed and pushed to a remote repository that it can access). Actually, the agent works on a copy of your repository that is uploaded to GitHub’s servers. So uncommitted changes are not included unless you explicitly share them.
- Perform actions that require your personal credentials (like deploying to production).
- Guarantee that its changes are correct—you must review everything.
Common Problems and How to Solve Them
Here are frequent issues users encounter:
- Agent not appearing: Update your IDE and the Copilot plugin. Also check that your subscription includes the agent (some legacy plans may not).
- Task fails with “Repository not found”: The agent needs access to your repository. Make sure the project is under Git and the remote is set. If your repository is private, ensure your GitHub account has access and that Copilot is authorized for that repo.
- Agent runs forever: Some tasks are too broad. Try to break them into smaller, more specific tasks. Also, check if the agent is stuck in a loop (e.g., running tests that never finish). You can stop it and refine your prompt.
- Changes not showing up: If the agent modifies files, but you don’t see them, check the “Agent” panel for a “View Changes” button. Sometimes the changes are staged in a separate branch or a special “Copilot” workspace.
- “Cloud agent is not enabled” error: Go to Settings > Tools > GitHub Copilot and ensure the “Cloud Agent” checkbox is ticked. Also, verify that you are signed in with a Copilot-enabled account.
Cost and Limitations
The cloud agent is included in your Copilot subscription—there is no extra per-use fee. However, there are usage limits: GitHub may impose rate limits on how many tasks you can run per hour or per day, depending on your plan. For example, free trial users may have a lower quota. Check your plan’s documentation for exact numbers.
Also, the agent uses cloud resources, so you must be online. If you have a slow connection, the agent may feel sluggish. Finally, the agent is not a replacement for code review—it can make mistakes, especially with complex logic or unfamiliar APIs.
Alternatives and Comparisons
If you don’t have access to the cloud agent, or if you prefer local processing, you have alternatives:
- Local Copilot Chat: The regular chat panel can do many of the same things, but it runs on your machine and often requires you to manually copy/paste code or use the “Apply” button. It’s faster for small questions but less autonomous for multi-step tasks.
- JetBrains AI Assistant: JetBrains offers its own AI assistant that integrates deeply with the IDE. It has similar features like code generation and refactoring, but it’s a separate product with its own pricing.
- Other AI coding tools: Tools like Cursor or Codeium offer agentic features, but they are not integrated into JetBrains as seamlessly as Copilot.
Frequently Asked Questions
Q: How is the cloud agent different from Copilot Chat?
Chat is a conversational assistant that responds to your prompts with explanations or code snippets. The cloud agent is more autonomous: it can execute a task end-to-end, including running commands and editing files, and then present a summary of changes.
Q: Does the cloud agent have access to my local files?
No, it works on a copy of your repository that is uploaded to GitHub’s servers. Uncommitted local changes are not included unless you explicitly share them (the agent may ask you to commit or push).
Q: Can I use the cloud agent on a private repository?
Yes, but you must ensure that your GitHub account has access to that repository and that Copilot is authorized to access it. You may need to grant permission in your GitHub settings.
Q: Is the cloud agent safe to use with sensitive code?
GitHub states that Copilot does not use your code to train models by default, but you should review your organization’s data protection policies. For highly sensitive projects, you might prefer the local chat or disable the cloud agent.
Q: Why did the agent make changes I didn’t expect?
The agent interprets your prompt, but it may misunderstand ambiguous instructions. Always review the diff before accepting. If the changes are wrong, you can reject them and rephrase your task with more specifics.
Q: How do I disable the cloud agent?
Go to Settings > Tools > GitHub Copilot and uncheck the “Cloud Agent” option. You can still use Copilot Chat and completions.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.