microsoft / microsoft/copilot-for-eclipse
Agent Mode cannot edit Eclipse Project Linked Resources (treated as outside workspace)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Feedback source
None
GitHub Copilot plugin version
0.14.0.202512112209
Eclipse IDE and version
Eclipse IDE for Embedded C/C++ Developers (includes Incubating components) Version: 2025-06 (4.36.0) Build id: 20250605-1316
Platform
Microsoft Windows NT 10.0.22631.0
x64
Steps to reproduce
- Create a linked resource pointing to an external directory (outside the workspace):
Window → Preferences → General → Workspace → Linked Resources → New - Create (or open) a project
- Add a Linked Folder pointing to the linked resource variable:
Project → New → Folder → Advanced → Link to alternate location (Lined Folder) → Variables... → choose the created variable from step 1. - Open a file in that linked folder
- In Copilot Chat (Agent Mode), request a small change
- Approve the Agent’s plan (if prompted)
Logs (optional)
No response
Expected behavior
Copilot Agent Mode treats Linked Resources as workspace files and applies edits directly (with normal confirmation flow).
Eclipse supports external sources via Linked Resources by design, and projects build/edit normally in this setup.
GitHub’s own Agent Mode announcements for Eclipse state the Agent applies changes via tools scoped to the workspace, which likely explains the strict boundary—but Linked Resources are conceptually inside the project workspace from the IDE’s perspective.
Actual behavior
Copilot Agent responds that it cannot edit files outside the active Eclipse workspace, naming the linked file path (e.g., C:\XXX\yyy.h).
No changes are applied, even though the file is open in the editor and is a valid Eclipse project resource.
Error like this:
I am unable to edit files outside the active Eclipse workspace. The file c:\XXX\yyy.h is not accessible for direct modification.
To proceed, please move the file into your Eclipse workspace, or let me know if you want the translated and revised content so you can manually copy it. I can provide the updated code for you to paste into your file if needed.
or this:
It appears the file path I used does not exist in the workspace. The file you are editing is located at: c:\XXX\yyy.h
Additional information
No response
Contributor guide
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.
Research direction
No source files or tests are named. Start by reproducing the linked-resource setup in Eclipse 2025-06 on Windows and trace how Agent Mode determines whether an open project resource is inside the workspace. Done means files reached through Eclipse Linked Resources can be edited through the normal Agent Mode confirmation flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100