Cody VS Code: Suggestions fail for inactive files after Godot Engine is opened

[AizenvoltPrime]

Version

Not specific to version(I use 1.89.1745454294)

Describe the bug

Description:

I've encountered a specific bug where Cody's chat file suggestion after you type @-filename stop working correctly in VS Code when interacting with a Godot Engine project under certain conditions.

The core issue seems to be triggered by having the Godot Engine editor running concurrently with VS Code accessing the same project files.

Steps to Reproduce:

1. Open a Godot Engine project folder directly in VS Code (without the Godot Engine editor running yet).
2. Open a project script file (e.g., a .gd file).
3. Verify that Cody's suggestions are working as expected within this file.
4. Keep VS Code open. Now, launch the Godot Engine editor and open the same project.
5. Wait for the Godot editor to fully load the project.
6. Go back to VS Code.
7. Click on the bottom right corner of VS Code to connect to GDScript language server.
8. The you get:
9. Try to trigger Cody suggestions in the file that was already open. Suggestions might still work here as it's an "active tab".
10. Now try to type @-filename of a file that is not on an active tab and you will get on the dropdown of suggestions "No files found"

Expected behavior

Cody file suggestions should continue to work reliably for all project files within the VS Code workspace, regardless of whether the Godot Engine editor is running and VS Code is connected to GDScript Language Server concurrently for the same project. Suggestions should appear for files whether they were already open in a tab or newly opened.

Actual Behavior:

After the Godot Engine editor is launched and loads the project, and VS Code is connected to GDScript Language server Cody file suggestions stop working for any file that is not currently loaded in an active VS Code tab.

Environment:

• OS: [Windows 11]
• VS Code Version: [1.99.3]
• Cody Extension Version: [1.89.1745454294]
• Godot Engine Version: [4.4.1]

Additional context

No response