Quick Verdict
GitHub Copilot for Eclipse is the official Microsoft-maintained plugin in microsoft/copilot-for-eclipse. It brings code completion, Next Edit Suggestions, Ask and Agent modes, MCP, Custom Agents, isolated subagents, Plan Agent, and Skills to Eclipse. The client source is MIT licensed, but the license applies to the plugin implementation, not the hosted generation service. Using completions, chat, and agents requires active GitHub Copilot access under GitHub’s separate free allowance, individual subscription, or organization plan.
It is the logical option for Java, enterprise, embedded, or plugin teams that must remain in Eclipse. The Marketplace currently lists Eclipse 2024-03 through 2026-03 and Windows, macOS, and Linux/GTK. Compatibility is still determined by the actual Eclipse distribution and its p2 bundles. Public Marketplace failures show missing or conflicting LSP4E, Mylyn WikiText, TM4E, Eclipse Core, UI, and editor dependencies on older or customized installations. Test on a clean installation matching production before broad rollout.
Best For
- Developers on Eclipse 2024-03 or newer who already have GitHub Copilot access.
- Java or enterprise teams that cannot move their established workspace to Cursor or VS Code.
- Desktop engineering teams capable of maintaining Eclipse p2 dependencies, proxies, certificates, and plugin compatibility.
- Not ideal for old Eclipse platforms, networks that cannot reach GitHub sign-in and Copilot services, or repositories prohibited from sending context to an external model.
Key Features
- Code completion: generate single-line or multi-line ghost text from editor context and natural-language comments.
- Next Edit Suggestions: predict the next edit location and propose changes based on recent work.
- Ask and Agent modes: Ask explains, generates, refactors, and debugs; Agent handles broader project-aware tasks and available tools.
- MCP integration: connect external tools and services in Agent Mode, subject to each server’s permissions.
- Advanced agents: Custom Agents, isolated subagents, and Plan Agent provide instructions, separate context, and task decomposition.
- Skills: discover
SKILL.mdfiles in workspace or user directories and enable or disable them in Eclipse Preferences. - Official distribution: install from Eclipse Marketplace or Microsoft’s documented update site.
- Open client: inspect and contribute to the MIT plugin source while the Copilot backend remains hosted.
Use Cases
- Generate boilerplate, tests, and local implementations in Java, Python, JavaScript, C, C++, and other supported editors.
- Ask for explanations and refactors using workspace context, then apply only small, reviewable diffs.
- Let Agent Mode plan cross-file changes and iterate on available command output while retaining Git diff and test gates.
- Validate Marketplace or update-site access, proxy behavior, certificates, and dependencies in a clean enterprise Eclipse image before managed deployment.
- Add MCP servers and Skills only after reviewing their files, shell, network, credential, and workspace permissions.
Pricing
| Component | License or price | Notes |
|---|---|---|
| Eclipse plugin source | Free, MIT | Client code can be inspected, modified, and contributed to |
| GitHub Copilot Free | Limited free allowance | Requires a GitHub account; current quotas are set by GitHub |
| Copilot individual paid plans | Subscription | Higher usage and plan-specific models or features |
| Copilot Business / Enterprise | Per-seat organization plans | Administration, policy, and enterprise capabilities |
Plugin releases and service billing have separate lifecycles. The official README says version 0.18.0 introduced internal support for an upcoming usage-based billing experience. Older clients may continue to work, but their usage panel and notifications may not accurately represent the latest billing experience. Follow the plugin changelog for compatibility and GitHub’s Copilot pages for purchasing and service terms.
Pros
- Official Eclipse client lets established teams add Copilot without changing their primary IDE.
- Completions, chat, Agent Mode, MCP, Skills, and planning cover both local suggestions and larger tasks.
- Marketplace entries support Windows, macOS, and Linux/GTK across several recent Eclipse releases.
- MIT source is reviewable, and Microsoft provides issue, support, and private vulnerability-reporting paths.
- Organization Copilot plans can place access under enterprise accounts and policy controls.
Cons
- MIT covers only the plugin source; AI use still depends on a Copilot account, quota, terms, and reachable service.
- Eclipse p2 dependencies are complex, and old Eclipse, STS, SAP, or embedded distributions can fail installation or editor integration.
- Agent Mode and MCP can read broader project context and invoke tools, increasing data-exposure and unintended-change risk.
- The README states that the plugin collects usage data and sends it to Microsoft, requiring privacy and policy review in regulated environments.
- Eclipse capabilities and release timing can differ from other Copilot clients; consult the official feature matrix rather than assuming parity.
Alternatives
| Tool | Best for | Difference from the Eclipse plugin |
|---|---|---|
| GitHub Copilot | Comparing the service across IDEs | Covers the overall service; this page focuses on Eclipse dependencies |
| Cursor | Teams able to adopt an AI-native editor | More centralized agent UX but requires an editor migration |
| Claude Code | Terminal and repository-level tasks | Avoids Eclipse p2 and uses a CLI-centered workflow |
| Codex | OpenAI coding-agent users | Different service and runtime, not an official Eclipse plugin |
| Windsurf | Users wanting an integrated agent IDE | Offers a cohesive editor but also requires migration from Eclipse |
FAQ
Does the MIT license make the Copilot service free?
No. MIT applies to the copilot-for-eclipse client source. Completions, chat, and agent backends require active Copilot access, with free allowances and paid plans provided separately by GitHub.
Which Eclipse versions are supported?
At this update, Marketplace lists Eclipse 2024-03 (4.31) through 2026-03 (4.39). A customized distribution based on a similar platform can still fail because its bundle versions, editors, or packaging differ.
Why does Marketplace report missing dependencies?
Typical causes include an old Eclipse platform, conflicting Mylyn or STS bundles, or update sources that cannot supply LSP4E, WikiText, TM4E, and related requirements. Upgrade and reproduce on a clean official installation rather than downloading unknown JAR files.
Are Agent Mode and MCP safe to enable?
They need controls. Review every MCP server, allowed directory, command permission, and credential. Require a plan and diff first, keep confirmation for terminal commands and external writes, and treat repository instructions as untrusted input.
Does the plugin collect telemetry?
The official README says it collects usage data and sends it to Microsoft to improve products and services. Review Microsoft and GitHub privacy statements, Copilot product terms, and organization-admin settings for the applicable details.
Bottom Line
GitHub Copilot for Eclipse fills a clear gap for teams that cannot leave Eclipse but want an official Copilot completion and agent client. Adoption requires separating three boundaries: MIT plugin code, the separately licensed Copilot service, and the local Eclipse/p2 runtime. Verify supported versions and dependencies first, test account and network access second, and enable Agent Mode, MCP, and Skills with least privilege. Persistent platform conflicts are better solved by upgrading or isolating Eclipse than by manually injecting dependencies.