Product overview
GitHub Copilot covers several different development jobs. In an editor, you can assess a suggestion while changing a file, or ask questions about nearby code. A task that starts with a repository issue can instead become agent work and a pull request to inspect. Choose the interaction around the change you need: explaining a function, editing a few files and delegating a repository task require different context and review.
The client matters. Supported IDEs provide interactive coding assistance; the CLI supports terminal work; the dedicated Copilot app brings agent tasks and repository work together; GitHub’s website keeps issues and pull requests close to the discussion. Features overlap, but support is not identical everywhere. Repository instructions, reusable skills and connected tools can add context where supported. Check the selected repository and the access you are giving that particular feature.
Usage also depends on the task. Chat and agent work consume GitHub AI Credits according to the model and work performed, while code completions and next edit suggestions are accounted for separately. Unlimited completions on a paid plan do not mean unlimited agent sessions or reviews. Agentic review enhancements can also use GitHub Actions runners. Judge a result through the actual diff, project checks and review coverage, rather than the confidence of an answer.
What GitHub Copilot offers
- 01Assess inline code suggestions and next edits in supported editing environments.
- 02Ask questions about files, repository structure and an intended code change.
- 03Work through a scoped implementation interactively with an agent in a supported client.
- 04Delegate eligible repository tasks to cloud agent work that can produce a pull request for review.
- 05Request code review feedback and suggested fixes where your plan and repository policies allow it.
- 06Supply repository instructions, reusable skills and relevant tool context through supported customization features.
A practical workflow
- 01Choose the surface and task: a local editing session, repository question, delegated change or code review.
- 02Provide relevant paths, expected behavior and failure details, then state constraints and completion checks.
- 03Inspect the proposed plan and resulting diff, and run the project’s relevant tests and build checks.
- 04Resolve review findings and remaining gaps before applying your repository’s normal merge process.
Summary based on source material; product claims have not been independently tested.
What makes it different
Connects development assistance with GitHub repository and pull request context across several work surfaces.
Who should consider it
- Developers who want assistance inside an editor they already use.
- Maintainers turning a well-defined repository issue into a reviewable change.
- Teams adding AI feedback to an established pull request process.
- Developers who prefer terminal-based work and explicit task boundaries.
What to verify
- The selected client supports the feature and your account or organization has enabled it.
- Repository, branch and connected-tool access match the intended task and your organization’s code-sharing rules.
- Changes preserve required behavior, authorization boundaries and supported dependency versions.
- Review coverage includes the files that matter; dependency manifests, lockfiles and other excluded types may need separate checks.
- AI Credits, any review-runner usage and applicable budgets are understood before a larger agent task.
Frequently asked questions
Are Copilot’s features the same in every editor?
No. Check GitHub’s feature matrix for your editor and client version. The Copilot app, GitHub website, CLI and IDE integrations serve overlapping jobs; GitHub Desktop’s commit assistance is another surface, rather than a guarantee of the same agent features.
Does a free account include every agent and review feature?
Copilot Free offers limited core use, while cloud delegation and standard code review have separate plan conditions. Organizations can also enable paid website reviews for members without individual Copilot licenses. Check the actual account and organization policy, and distinguish completion limits from AI Credits.
Does a Copilot review mean a change is ready to merge?
A review can miss problems and does not establish that your project’s tests passed. By default, Copilot’s approval does not satisfy required approvals, although administrators can configure approvals that do. Verify the diff, review coverage and actual repository checks, and supplement AI feedback with human review.
How can I make the advice fit an existing repository?
Provide the relevant files and a precise goal, then use supported repository instructions, skills or connected context for project conventions. Keep tool permissions and private-code sharing within your organization’s rules. More context does not remove the need to verify a proposed change.
Explore related tasks
Product facts were checked against the official product website or its first-party documentation on Nov 4, 2026.
