GitHub Copilot

GitHub Copilot comes from GitHub (part of Microsoft). It was the first AI coding assistant to reach wide adoption and still has the broadest editor support: official plugins for VS Code, the JetBrains suite, Neovim and Visual Studio. When a team is split across editors, it is often the only option everyone can actually use.

It is at its best continuing what you started — you write the signature or a comment, it fills in the rest. Repetitive code (test cases, data transforms, boilerplate config) is where the time saving is most obvious. Over the last few years it has grown beyond completion into chat, multi-file edits and code review, and its ties to GitHub repositories and pull requests are hard for anyone else to match.

Worth knowing going in: the completions look plausible without always being correct, particularly around edge cases and error handling. Treat it as a fast but careless pair — every line still needs reading before it stays.

Key features

• Inline completion: grey suggestions appear as you type and Tab accepts them. This is its core and most mature capability.
• Copilot Chat: ask questions, explain code or generate tests from a sidebar, referencing the current file or a selection.
• Agent mode: in supported editors, describe a task and it edits across files and tries running commands to check the result.
• GitHub integration: it can summarise and review pull requests, and you can hand it an issue to draft a PR.
• Model choice: subscribers can switch between models from different vendors to suit the task.

How to use

1. Sign in to GitHub and enable the free tier or a subscription on the Copilot page; students and open-source maintainers can apply for free access first.
2. Search for “GitHub Copilot” in your editor’s extension marketplace, install it and sign in when prompted.
3. Write code as usual: Tab accepts a suggestion, Esc dismisses it. A descriptive comment noticeably improves what it suggests.
4. For explanations or refactors, open the Copilot Chat panel, select the code and ask.

Best for

• Teams on mixed editors: the plugin coverage means nobody has to switch editors to get AI help.
• Lots of repetitive code: test fixtures, field mappings and config files are where completion pays off most directly.
• Teams that live on GitHub: PR summaries, reviews and issue workflows connect directly.
• Students and open-source maintainers, who can use it for free if eligible.

Strengths and limitations

Strengths

• The widest editor support, including official JetBrains and Neovim plugins.
• Fast, unobtrusive completions that fit your existing rhythm.
• Deep GitHub integration, with straightforward team management and billing.

Limitations

• Plausible-looking completions are not always correct; edge cases and error handling need human review.
• Changes that need an understanding of the whole project feel less capable than in dedicated tools like Cursor or Claude Code.
• Reachable from mainland China, though speed depends on your connectivity to GitHub.