[Feature Request] Copilot CLI Quick Launcher (Just like Intellij) with WSL & Auto-Install Support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
Research direction
Start by examining the GitHub Chat view, toolbar, and Eclipse terminal entry points named in the issue, along with how the extension currently launches external commands. Compare the existing IntelliJ behavior and investigate Windows-to-WSL path and process handling. Done means a project-root launch, missing-CLI guidance, and a configurable WSL execution path are defined and covered by appropriate tests.
Written by the indexing model from the issue text.
Description
Problem Description
When using the GitHub Copilot extension in Eclipse, there is no quick, integrated way to transition from GitHub Chat, the toolbar, or the terminal into the GitHub Copilot CLI scoped to the current project. While similar functionality exists in IntelliJ—including helpful guidance to install the GitHub CLI if it is missing—Eclipse users currently lack this seamless shortcut. Additionally, for Windows developers whose projects reside inside WSL (Windows Subsystem for Linux), the Copilot CLI is often installed inside the WSL environment rather than natively on Windows, making a standard Windows execution path fail.
Proposed Behavior
Integration Button: Add a button in the GitHub Chat view, toolbar, or Eclipse terminal that opens the GitHub Copilot CLI.
Project Context: Automatically set up the terminal session to point to the current project's root directory.
Auto-Install Guidance: Include helper functionality to guide the user through installing the GitHub CLI if it is missing (matching the existing IntelliJ implementation).
WSL Configuration Option: Provide an extension configuration setting to allow launching the Copilot CLI inside WSL (e.g., via wsl.exe) when the CLI is installed in the WSL environment rather than on the Windows host.
Use Case & Motivation
Use Case: A developer working on a project in Eclipse on Windows (with their workspace or development tools hosted inside WSL2) wants to click a single button in GitHub Chat to launch the Copilot CLI right where they are coding, without manually opening an external terminal, navigating paths, or dealing with Windows-to-WSL environment translation.
Motivation: Bring feature parity between the Eclipse Copilot extension and other IDEs like IntelliJ, significantly reducing friction for developers and streamlining AI-assisted terminal workflows, especially for those utilizing WSL development stacks.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/copilot-for-eclipse
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#472 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#465 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/copilot-for-eclipse#458 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#450 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
[Feat] Expose/allow configuration of github.copilot.chat.virtualTools.threshold in Eclipse CopilotOpenenhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#449 ·
Maintainers usually reply within 1 day
All issues in microsoft/copilot-for-eclipse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days
-
area:cpan-port area:database bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fglock/PerlOnJava#1605 ·
Maintainers usually reply within 1 day
-
1.0.0-rc2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#377 ·
Maintainers usually reply within 1 day
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day