Text of docs.github.com › en › copilot › concepts › copilot-surfaces › copilot-on-github as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

GitHub Copilot on GitHub.com and GitHub Mobile - GitHub Docs

Skip to main content Skip to content Collapse sidebar Expand sidebar GitHub Copilot on GitHub.com and GitHub Mobile Move from repository questions to planned code changes and review in one continuous session with GitHub Copilot on GitHub.com and GitHub Mobile. In this article On the GitHub website and GitHub Mobile, GitHub Copilot can answer questions about your repositories, plan and make changes, review pull requests, and automate repository tasks.

You can ask questions and delegate work from a conversation, and use Copilot directly in your issue and pull request workflows. With the new Copilot in the cloud experience, you can move between web or mobile and local clients (Copilot app, VS Code, or Copilot CLI), working with and steering Copilot in the same session. Note Starting October 28, 2026, the new Copilot in the cloud experience on GitHub.com and GitHub Mobile is available to users with a paid Copilot plan, subject to applicable organization and enterprise policies.

Users on Copilot Free plans will continue to use the old Copilot Chat experience. This article explains both the newer Copilot in the cloud experience and the older Copilot cloud agent plus Copilot Chat experience. For a quick overview of what's changing, see Comparison of the two experiences . How Copilot helps on GitHub.com and GitHub Mobile You can combine chat, agentic work, code review, and automations in your repository workflows.

For example, you might use chat to understand how a repository handles authentication, then ask Copilot to plan and add missing tests. Once the changes are in a pull request, you can request a review from Copilot. To maintain test coverage over time, you could set up an automation to check for missing tests each week and propose additions for you to review. Key concepts for Copilot in the cloud Copilot in the cloud allows for a continuous task flow.

Copilot sessions that you start on in a cloud environment on GitHub can continue seamlessly across different clients, such as the GitHub Copilot app, your IDE, mobile, and CLI. Your work and context are preserved across these clients, meaning you can move from asking questions to agentic work to task completion, in the same conversation. Client, session, and environment There are three key components to understand in the task flow: the client, the session, and the environment.

To start an agent task, you interact with Copilot through a client or surface, such as the web interface, GitHub Copilot app, IDE, GitHub Mobile, or GitHub Copilot CLI. A session is the conversation and activity associated with agentic work, including the prompts you provide and the responses generated by Copilot. An environment is the place where the agent executes its work, such as a cloud sandbox, a GitHub Actions runner, or a remote custom environment.

For more information, see About cloud sandboxes for GitHub Copilot , About local sandboxing for GitHub Copilot , and GitHub Copilot in IDEs . Session context You can start a chat session with the following contexts automatically attached: All repositories, owned by you or by an organization. A specific file, issue, pull request. A specific repository and branch. A space. You can attach context with the repository selector, the + menu, or @ mentions.

To let Copilot retrieve information from supported services during a task, use customizations such as Copilot connectors and personal custom Model Context Protocol (MCP) servers. Session context is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see About GitHub Copilot Memory . Sessions across surfaces Choose a cloud sandbox when you want to continue a session across supported Copilot surfaces.

You can start a cloud session on one surface and continue it on another. Comparison of GitHub Actions-based sessions and cloud sandboxes In Copilot in the cloud, you have three environment choices: Cloud (a cloud sandbox), GitHub Actions-based, and Remote (a connection to a custom environment). Initial performance testing on GitHub indicates that sessions in cloud sandboxes completed execution faster on average than GitHub Actions-based sessions.

The following table compares GitHub Actions-based sessions and cloud sandbox-based sessions. GitHub Actions Cloud sandbox Session continuity Sessions are only available on the GitHub website. Sessions can be shared and resumed across clients. Repository scoping Sessions require a repository. Changes are made only in the specific, single repository context. Sessions can span across repositories in one organization. Changes can be made across multiple repositories Chat data retention Data is retained for 28 days.

Data is retained for the life of the account. Custom environments Supports GitHub Actions-specific custom compute, network and setup configuration, and self-hosted runners. Cloud sandboxes honor repository and organization firewall allowlists, but do not support custom compute, GitHub Actions-specific setup steps, or self-hosted runners. Customizations and tool sharing Supports custom instructions, MCP servers, and content exclusions.

Supports custom instructions, dotfiles personalization, repository and personal MCP servers, connectors, and content exclusions with a single configuration across all cloud sandboxes. Why choose this environment Suitable when you need repository-specific integrations, custom environments, or self-hosted runners. Suitable for cross-repository chat, quick access to AI models, and when custom compute or network configurations are not required in cloud sandboxes.

In the Copilot in the cloud experience, cloud and GitHub Actions compute draw on the same monthly GitHub account allowance, separate from AI credits. For details, see Billing for cloud and local sandboxes for GitHub Copilot . Access and availability Available Copilot features depend on your plan and organization policies. For setup guidance, see Set up Copilot . For usage allowances and costs, see GitHub Copilot billing and usage .

Repository owners and administrators can disable Copilot for particular repositories, even when your plan and policies otherwise allow you to use it. Organization and enterprise policies continue to apply. See Managing GitHub Copilot in the cloud for your enterprise or organization . To view organization data or sessions, you must meet your organization's single sign-on requirements. Without write access to a repository, your Copilot session is read-only.

Starting with Copilot on GitHub.com and GitHub Mobile You can start working with Copilot from several different entry points: Your Copilot home page at github.com/copilot The Copilot panel, displayed when starting a session within a file, issue, or pull request Your GitHub dashboard at github.com The Agents tab or panel within a repository Ways to work with Copilot You can work with Copilot in several ways: Asking questions Chat can explain unfamiliar code, suggest fixes, generate tests, or compare approaches.

Follow-up questions let you refine your request without starting a new conversation. Chat is preconfigured with tools for tasks such as creating branches, updating files, and creating or updating issues. It also supports semantic code search, limited to default branches only. Agentic work Copilot can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in a cloud development environment, rather than your local IDE.

When you ask for changes, Copilot works against the repository and branch you provided. You can review the proposed changes and ask for refinements before creating a pull request, or request a pull request in your prompt. From security campaigns, you can assign code scanning alerts to Copilot for fixes. See Fixing alerts in a security campaign . Code review On GitHub, Copilot code review reviews pull request changes, identifies potential

The rest of this page is on the live site.