GitHub Copilot in Eclipse: Setup and Project Instructions
GitHub Copilot supports Eclipse through a plugin that adds inline code completions and a chat panel. Here is how to install it, check compatibility, and give your project context to any connected assistant.
Updated 5 min read
GitHub Copilot is available in Eclipse through an official plugin that adds inline completions and a chat panel to the IDE. The plugin uses the Language Server Protocol to communicate with the Copilot service. Tools like fenbs work alongside the IDE to keep project requirements, architecture decisions, and task context in a shared record that any connected assistant reads before starting, independent of which IDE the developer is using that day.
Eclipse compatibility
The GitHub Copilot plugin for Eclipse requires a recent Eclipse IDE release. Open Help > About Eclipse IDE to check your version. If you are on an older version, update Eclipse from eclipse.org before installing the plugin. The plugin also requires Java 17 or later to be installed on your system, as it uses a language server process that runs separately from the IDE itself.
You need a GitHub account with an active Copilot subscription or access through an organization. Confirm your access on GitHub.com under your account settings before starting the installation.
Install the GitHub Copilot plugin for Eclipse
- Open Eclipse and go to Help > Eclipse Marketplace.
- Search for "GitHub Copilot" in the Marketplace search box.
- Find the official GitHub Copilot plugin and click Install.
- Follow the prompts to accept the license agreement and restart Eclipse when the installation completes.
- After restarting, open the GitHub Copilot sign-in dialog from the bottom status bar or from the Window menu. Follow the browser flow to authorize your GitHub account.
If the plugin does not appear in the Eclipse Marketplace, you can install it from an update site URL. Check the GitHub Copilot documentation (opens in a new tab) for the current Eclipse plugin update site, as the URL may change between versions. In a corporate environment, a proxy or firewall may block the Marketplace connection; contact your IT team if the download fails.
Verify the plugin is working
After signing in, open a Java project and start typing in a source file. Gray inline suggestions should appear as you type. Press Tab to accept a suggestion or Escape to dismiss it. If no suggestions appear after a few seconds of typing, check the Copilot status indicator in the Eclipse status bar at the bottom of the window.
Open the Copilot Chat panel from Window > Show View > Other > GitHub Copilot. Ask it a question about your open file, such as "What is the purpose of this method?" or "How can I improve the null handling here?" The chat panel uses the currently open editor as context.
First assisted coding task in Eclipse
A reliable first task is writing a test for an existing class. Place the cursor in a test file, start typing a test method name for a class you want to cover, and let Copilot suggest the structure and assertions. Review the suggestions carefully: Copilot generates plausible code but does not know your specific business logic or expected values. Run the tests and fix any that fail due to incorrect assumptions.
For refactoring an existing method, select the code in the editor, open the Copilot Chat panel, and ask it to suggest improvements. The chat gives you an explanation alongside the suggested code, which is more informative than a silent inline completion for understanding why a change is being suggested.
Giving Copilot project context in Eclipse
Copilot's suggestion quality depends on the files you have open. Open the most relevant source files before asking complex questions about the project. Eclipse's indexed search can help you find the right files quickly. If your project follows a specific architecture or uses patterns that differ from typical examples, describe those in the chat rather than expecting Copilot to infer them.
For alternative AI coding tools if Copilot does not suit your Eclipse workflow, see GitHub Copilot alternatives. For more information on available Copilot models, see GitHub Copilot models.
Keep project requirements beyond any single IDE session
fenbs stores the architecture decisions, naming conventions, and task context for your project outside the IDE. When you switch from Eclipse to another tool, or when a colleague picks up a task you started, the project record is in fenbs rather than scattered across open editor tabs and chat histories. Connect a supported assistant from Integrations and it reads the project context before starting.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add a project for the codebase you are working on in Eclipse.
- Write key architecture decisions as Decisions and rules: the Java version, the frameworks used, package naming conventions, and any prohibited patterns.
- Add tasks for current features and bugs on the kanban board, with a brief plan for each.
- At the start of a session, read the project's Where we left off and current tasks before opening Eclipse so you start from the current state.
- Connect a supported AI assistant from Integrations so it reads the project context before you ask it to generate or review code.
fenbs does not connect to Eclipse directly. It keeps the team's project decisions and task state in a record any connected AI can read. For using Copilot from the command line alongside your Eclipse work, see GitHub Copilot CLI.
If you need to reuse project prompts or standard code instructions across multiple developers working in Eclipse, store them as Skills and prompts in fenbs. Any connected assistant can list and read them at the start of a session, so the same prompt does not have to be retyped or shared over email.