Option to fully disable automatic edits to All Files

[hsyhhssyy]

Some time ago, I opened a PR suggesting an option to completely disable the plugin’s behavior of modifying users’ file PackageName and ClassName. As far as I remember, it was closed at the time because there did not seem to be a clear use case.

Recently, I came across a scenario where this option could be genuinely useful: Copilot Agent Mode. In Agent Mode, the AI may try to create files from scratch and fill in their PackageName and ClassName on its own. I found that in some cases, the plugin then changes those values afterward, and Copilot may interpret the resulting file as incorrect and start editing it again. This can lead to unnecessary rework.

That behavior may also lead to additional token usage. While Copilot itself may not be billed by token usage, the plugin can also work with other tools such as Claude, where those extra edits may result in avoidable token costs.

Because of this, I think it could be helpful for the plugin to provide an option to fully disable all automatic file editing behavior, so users who prefer to let the AI handle everything can do so.

Even Copilot provides a way to disable Inline Copilot, partly to avoid extra suggestions and unnecessary token usage while using Agent Mode and simply browsing code. For a similar reason, having a full opt-out here might be useful for some workflows as well.

[isc-bsaviano]

Hi @hsyhhssyy, can you share a screenshot or recording of the behavior you are seeing? Classes and routines that are created with content in them already will not be modified by the latest version of this extension. That behavior has been removed.

[hsyhhssyy]

I haven’t seemed to encounter this issue recently, so it may have been resolved by a plugin update. I’ll close this issue for now, and if it happens again, I’ll reopen it with screenshots.

[hsyhhssyy]

Recently, I noticed this seems to be happening again.

Please refer to the screenshot above.

This file is generated automatically by Copilot.

The chat log is shown below.

In the diff during creation, it shows that the AI generated this file starting from just a blank line.

However, when checking the final disk component, there are some blank file content before the AI-generated content.

[hsyhhssyy]

I have a possible guess — could it be related to fluctuations in my network connection? Recently, I’ve occasionally been disconnected from the server and then reconnected very quickly. Sometimes VS Code shows a network connection error, but when I switch to the Server Panel, everything appears normal again. Could VS Code run into problems writing files if the server connection drops or changes status?

[isc-bsaviano]

@hsyhhssyy This feature does not depend on a server connection. I think this is caused by some assumptions about behavior not holding when AI instead of a human is making changes. The code waits 100ms before checking the content in case VS Code quickly created the file, then filled in content (for example, as part of a move). However, the AI could take much longer than that and it clearly isn't smart enough to check the file contents before making the edit or to blow everything away. As much as I loathe to add new setting,s once might be needed here.