microsoft / microsoft/copilot-for-eclipse

[Bug] Copilot sometimes makes changes, but then says that the changes

Open
#155 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Description

Environment

  • OS: Windows 11 25H2
  • Eclipse Version: 2025-06
  • Plugin Version: 0.16.0.202604020254

Describe the bug
When using Agent mode to edit files using Claude sonnet 4.6 (though I have noticed it with other models as well), Copilot first says "I'm going to do X", then performs the necessary changes, but then re-reads the file and sees that the changes has already been made, and then it reads the file multiple times to verify what's going on, only to try and gaslight me by saying the file was originally already in the final state. To be clear: the change does get made, but Copilot thinks the final state was how the file originally already was.

To Reproduce
Steps to reproduce the behavior:

  1. Ask Copilot to make a change to a file, like inserting an extra layer of divs inside a document tree.

Expected behavior
I expect Copilot to not pretend like it didn't need to edit the file, and instead say that it has edited the file according to my request.

Screenshots

Image

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Eclipse 2025-06 with Copilot plugin 0.16.0.202604020254 using Agent mode and a request that edits a file, such as inserting nested divs. Observe the edit and subsequent file reads; done means Copilot accurately reports that it changed the file instead of claiming the final state was present originally.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.