GitHub Copilot for Eclipse is now open source under MIT
GitHub has opened the Copilot for Eclipse plugin source, giving Java and Eclipse teams a clearer view of chat, completions, agent mode, MCP integration, skills, and BYOK behavior.
What changed
GitHub Copilot for Eclipse is now open source, with the plugin code published under Microsoft’s GitHub organization and licensed under MIT. GitHub’s announcement says the repository exposes the implementation behind completions, Next Edit Suggestions, chat, agent mode, skills, prompt files, BYOK, custom agents, isolated subagents, plan agent, and MCP integration. For Eclipse-heavy teams, the release turns Copilot from a closed IDE extension into a codebase they can inspect before adopting deeper agent workflows.
Key takeaways
- The GitHub changelog confirms that Copilot for Eclipse is open source and points to the public
microsoft/copilot-for-eclipserepository. - The repository README describes support for code completions, Next Edit Suggestions, Ask Mode, Agent Mode, MCP integration, custom agents, isolated subagents, plan agent, and skills.
- The Microsoft Java blog previously announced the open-source move and now links to the live repository as the place to explore and contribute.
- The plugin still requires an active GitHub Copilot subscription for use; open source does not make the Copilot service itself free.
Practical LinkLoot angle
This is more useful than a normal extension announcement because it gives teams a reviewable reference implementation for agentic IDE features in Eclipse. If your organization has conservative Java estates, regulated code, or long-lived Eclipse workflows, the source lets you inspect how project context, skills, prompt files, MCP tools, and agent handoffs are wired before enabling broad usage.
| Component | Best use | Limitation | Source |
|---|---|---|---|
| Copilot for Eclipse repository | Inspect plugin behavior, build process, and contribution path | Service access still depends on Copilot subscription | GitHub repository |
| Agent Mode and subagents | Evaluate larger project-aware coding workflows inside Eclipse | Needs governance around tool access and context sharing | Repository README |
| Skills and prompt files | Standardize team-specific instructions for Java projects | Skill content should be reviewed like code | Repository README |
| MCP integration | Connect Copilot workflows to external tools | External tools expand the security review surface | GitHub changelog |
For LinkLoot readers, the immediate workflow is simple: clone or browse the repository, map the agent features to your team’s IDE policy, then test in one Eclipse workspace before enabling MCP tools or custom skills in shared projects.
What to verify before you act
Check the repository license and security policy directly before redistributing modified plugin builds. Confirm which plugin version your Eclipse users run, because the README notes that version 0.18.0 and later includes internal support for GitHub’s upcoming usage-based billing experience. If you plan to enable MCP or custom skills, review those configurations separately; open-sourcing the plugin does not automatically make every connected tool safe.
No. The plugin source is open under MIT, but using Copilot still requires an active Copilot subscription or approved access.
If you are comparing agentic developer tools, LinkLoot’s AI agent tools guide is a good next checkpoint.