#GitHub Integration

Copilot is not only an IDE extension. The same account on github.com can answer questions about files, Issues, and pull requests, draft PR summaries, and review changes. The hub is still the Copilot docs. Website Quickstart: Quickstart for GitHub Copilot (GitHub website tab).

Windows and macOS both use the browser—there is no separate “web installer.” The only difference is which editor you use later to pull the branch.

#Ask from a file view

1. Open a file in a repository.
2. Click the Copilot icon at the top right to open the Chat panel.
3. Type a question and press Enter. Official examples:

Explain this file.
How could I improve this code?
How can I test this code?

Follow up with tell me more. Start a new topic with + in the panel so old turns do not pollute context.

This is for “glance at a repo in the browser” without cloning. Answers can still be stale or miss private modules—treat them as leads, then verify in the IDE or tests.

#Issues: ask, draft, assign the agent

Open the same Copilot panel on an Issue:

Summarize this issue for a developer who has never seen the repo.
What files are likely involved? Cite paths only if you can see them.

Copilot can also help create or update Issues from natural language or images—see Using GitHub Copilot to create or update issues. A human still edits title, labels, and repro steps.

To hand implementation to the cloud agent: Assignees → Copilot. Rules and limits are in Coding Agent—after assignment, follow up on the PR, not with Issue comments only humans will see.

#Pull requests: summary, Q&A, review

#Generate a description summary

When creating or editing a PR, open the Copilot menu in the description field header and choose Summary. GitHub notes Copilot does not read text already in the description, so a blank box yields a cleaner draft. You still add why it changed, how to test, and risk.

Docs: the Copilot summary section in Helping others review your changes.

#Chat about the PR

Click the Copilot icon on the PR page; the PR is attached as context. For example:

Summarize this pull request
What are the main changes in this pull request?
What problem does this pull request solve?

Tutorial: Using GitHub Copilot to explore pull requests. You can include a commit SHA, e.g. What changed in commit a778e0eab?.

#Copilot code review

GitHub can have Copilot review PRs and suggest one-click fixes. Availability and defaults depend on plan and org settings—see About GitHub Copilot code review and Using GitHub Copilot code review on GitHub.

Official constraints:

• Copilot reviews do not replace required human review counts
• You still read the diff: logic bugs, secrets, dependency changes
• Review PRs opened by Copilot with the same bar (Review output from Copilot)

Admins can configure when review runs and which runners to use (Configuring code review by GitHub Copilot).

#Agents panel and /task

The Agents control in the site chrome, github.com/copilot/agents, and /task in Chat all start cloud sessions. Pick a repo, write a prompt, optionally attach images, then watch the session. This does not need your IDE; a sleeping laptop does not stop the cloud job (plan and policy still apply).

#GitHub MCP and Chat

On github.com, Copilot Chat can use the GitHub MCP Server to perform GitHub actions from the thread (create a branch, search users) with “no extra setup.” Trust Using the GitHub MCP Server from Copilot Chat. That is not a blank check on every repo—your GitHub permissions and org policy still apply. Rolling your own MCP is this site’s MCP course.

#Mobile

GitHub Mobile includes Copilot Chat. Business / Enterprise may search a wider knowledge scope on mobile (for example org knowledge)—see the current feature matrix. Do not approve an Agent PR from a phone without reading it.

#How this meets the local loop

Still keep secrets out of Issue bodies. If the agent needs private resources, follow Configure secrets and variables for Copilot cloud agent—do not paste tokens into comments.

#Next

• Copilot CLI
• Coding Agent
• Copilot vs Cursor