GitHub Copilot on GitHub.com

Explore your repositories, plan changes, and delegate coding tasks to GitHub Copilot without leaving GitHub.com.

이 기사에서

GitHub Copilot on GitHub.com 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 the same prompt box, or use Copilot directly in your issue and pull request workflows.

To compare where you can use Copilot, see GitHub Copilot 사용할 위치.

How Copilot helps on GitHub.com

You can work with Copilot in several ways:

  • Chat lets you ask questions about your repositories, understand code, and explore possible solutions.
  • Agentic experiences can research a repository, plan changes, and complete multi-step tasks by reading files, editing code, and running tests in a cloud development environment.
  • Code review provides feedback on pull requests and suggests fixes.
  • Automations run repository tasks on a schedule or in response to events, rather than requiring a new prompt each time.

For example, you might use chat to understand how a repository handles authentication, then ask an agent 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.

Chat and agentic experiences

On GitHub.com, you can move from asking questions to delegating work in the same conversation.

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.

Delegating work

Copilot cloud agent can research a repository, plan changes, and implement them in the background. It can edit files and run tests and linters in an ephemeral cloud development environment, rather than your local IDE. See GitHub Copilot in IDEs.

You can start work from the agents panel, a conversation, or an issue or pull request on GitHub.com.

From security campaigns, you can assign code scanning alerts to Copilot for fixes. See 보안 캠페인에서 경고 수정.

When implementing changes, Copilot handles branch creation, commit messages, and pushing changes. You can review changes and request refinements before creating a pull request, or request a pull request in your initial prompt. You can also continue the work yourself. See 코드 변경 사항을 연구하고, 계획하고, 반복 작업을 수행하세요. Copilot cloud agent을(를) 사용하여..

Session context

On GitHub.com, Copilot Chat and Copilot cloud agent can share context. When you start an agent session from a chat, the session incorporates the context of your conversation. While the session runs, you can continue chatting with Copilot about its progress and steer the work.

Copilot Chat can also answer questions about pull requests created by Copilot by pulling in the relevant agent session logs. You can ask what changed, what was validated, and why, without leaving the conversation.

This context passing is scoped to the Copilot Chat and cloud agent sessions you are actively working with. It is distinct from Copilot Memory, which builds a longer-term, persistent understanding of your repositories and preferences across sessions. For more information, see GitHub Copilot 메모리 정보.

On GitHub.com, session logs show the work and tools used. Shared sessions and pull requests let teammates with repository access follow the work and review changes. Logs do not replace your own review and testing. See 에이전트 세션 관리.

Sessions across surfaces

With remote control enabled, you can monitor and steer a GitHub Copilot CLI session from GitHub.com. It continues running on your original machine, which must stay online. See GitHub Copilot CLI 세션의 원격 제어에 대한 정보.

On GitHub.com, you can ask about your synced session history across Copilot surfaces. This includes Copilot cloud agent and Copilot code review sessions, and sessions from GitHub Copilot CLI, VS Code, JetBrains IDEs, and the GitHub Copilot app.

You can only query sessions you started. Syncing must be enabled and permitted by your organization's policies. See Query past sessions.

Code review

On GitHub.com, Copilot code review reviews pull request changes, identifies potential issues, and suggests fixes. It uses agentic capabilities to gather context from your repository. You can request a review or configure automatic reviews, then review and apply the suggested changes. See GitHub Copilot 코드 검토 정보.

Copilot can also generate a summary of your changes directly in a pull request description or comment. This helps reviewers understand the changes, but is separate from reviewing the code. See GitHub Copilot 사용하여 끌어오기 요청 요약 만들기.

Automations and agentic workflows

Automations let you define a task once and have Copilot cloud agent run it on a schedule or in response to repository events. For example, an automation can triage incoming issues or prepare weekly release notes. You create and manage automations from the Agents tab in a repository on GitHub.com. Automations are available in eligible private and internal repositories. See Copilot 자동화 정보.

GitHub Agentic Workflows provide another way to automate tasks in your repositories on GitHub.com. You define tasks in natural language in Markdown files, and they run as GitHub Actions workflows. These workflows can use Copilot or another supported coding agent. See GitHub 에이전트 워크플로 정보.

Customizations

On GitHub.com, custom instructions let you save personal preferences for chat, repository conventions, and organization guidance. Copilot Spaces organize shared context for questions. For delegated work, custom agents and agent skills provide task-specific instructions and resources. Model Context Protocol (MCP) servers connect agents to additional tools and data. Hooks can run commands during agent work for validation or logging. For setup guidance, see 사용자 지정 Copilot.

AI models

응답을 생성하는 데 사용하는 모델을 Copilot 변경할 수 있습니다. 질문 유형에 따라 다른 모델이 더 잘 수행되거나 더 유용한 응답을 제공할 수 있습니다. 옵션으로는 고급 기능을 갖춘 프리미엄 모델이 있습니다. IDE에서 모델을 변경하려면 GitHub Copilot Chat의 AI 모델 변경을 참조하세요. 모델을 GitHub변경하거나 비교하려면 GitHub에서 GitHub Copilot에 질문하기을 참조하세요.

On GitHub.com, available models depend on your plan and account policies. See GitHub Copilot에서 지원되는 AI 모델.

For Copilot cloud agent, the ability to select a model also depends on how you start the task. See GitHub Copilot 클라우드 에이전트에 대한 AI 모델 변경.

References to matching public code

In chat responses and agent sessions on GitHub.com, Copilot can generate code that matches code in public repositories. Code references help you review the matching code and its licensing information so you can decide whether to use it, provide attribution, or remove it.

Matches appear in the context where you are reviewing the output:

  • Chat responses: If you or your organization allow suggestions matching public code, matching code in a response includes a reference beneath the suggestion. The reference identifies public repositories containing matching code and licensing information, if found.
  • Agent session logs: When Copilot generates matching code during a delegated task, the session logs include a link to details of the matched code.

Matches occur infrequently, so most responses do not contain code references. The search covers an index of public repositories on GitHub.com, not private repositories or code hosted elsewhere. The index is refreshed periodically, so it may omit recently added code or refer to code that has since moved or been deleted.

For instructions on viewing references, see GitHub Copilot 제안과 일치하는 공용 코드 찾기.

Access and availability

Available features depend on your plan and organization policies. For setup guidance, see 설정하기 Copilot. For usage allowances and costs, see GitHub Copilot 청구 및 사용량.

Repository owners and administrators can disable Copilot cloud agent for particular repositories, even when your plan and policies otherwise allow you to use it. See GitHub Copilot 클라우드 에이전트에 대한 액세스 관리.

Limitations and compatibility

Both chat and agentic experiences on GitHub.com can produce incorrect or suboptimal code, including code that contains security vulnerabilities. Review and test the output before using it in production. See 애플리케이션 카드: GitHub Copilot 에이전트.

For information about built-in security protections, see GitHub Copilot 클라우드 에이전트에 대한 위험 및 완화.

Agentic work

Copilot cloud agent has the following workflow limitations:

  • Repository scope: Copilot can only make changes in the repository specified when you start a task. It cannot make changes across multiple repositories in one run.

  • Context access: By default, the GitHub MCP server only provides access to context in the repository where the agent is working, such as issues and previous pull requests. You can configure broader access through repository MCP settings. See 리포지토리에 대한 MCP 서버 구성.

  • Branches and pull requests: Copilot can only work on one branch at a time and can open one pull request per task.

  • Session duration: Each Copilot cloud agent session has a maximum execution time of 59 minutes. This limit cannot be extended or bypassed. If a task exceeds the limit, the session times out and stops.

    Break complex tasks into smaller, focused tasks. You can configure a shorter timeout using the timeout-minutes setting in your copilot-setup-steps.yml file. See 개발 환경 구성.

Repository compatibility

  • Repository rules: If a ruleset or branch protection rule is incompatible with Copilot cloud agent, access to the agent is blocked. For example, a rule that only allows specific commit authors can prevent Copilot from creating or updating pull requests. If the rule is configured using rulesets, repository administrators can add Copilot as a bypass actor to enable access. See 리포지토리에 대한 규칙 세트 만들기.
  • Repository hosting: Copilot cloud agent only works with repositories hosted on GitHub. It cannot work on repositories stored on other code hosting platforms.

Further reading