Amazon Q VS Code Extension Fails to Open Files on Windows — %5C Encoded Path Issue

[PavithranThavamani]

After updating to the latest version of the Amazon Q VS Code extension, the "Review Changes" action fails to open files in the editor on Windows.

Steps to reproduce the issue

Install the latest Amazon Q extension on Windows.

Open a project (with typical Windows paths, e.g. C:\Users\Username\Project).

Trigger Review Changes.

VS Code shows error and file cannot be opened.

Expected behavior

The extension should decode %5C backslashes or use forward slashes (/) so that file paths resolve correctly on Windows.

System details (run AWS: About and/or Amazon Q: About)

• OS:
• Visual Studio Code version:
• AWS Toolkit version:
• Amazon Q version:

[ashishrp-aws]

fix for the issue: #8047. Releasing this Thursday in next update.

[Huzaifa100203]

I'm facing the same issues as The Agentic Mode Edits a File but after the Edits I can't see the changes it did in the Files and it shows The editor could not be opened due to an unexpected error. Please consult the log for more details. and in the logs it shows
Unable to resolve resource and the File path which is correct but still it shows the File couldn't be found

[lynzleb]

I experience this with Amazon Q Developer 1.94, switched back to 1.93 in the meantime and problem is not there.