I have checked the following:
This bug is:
Bruno version
4.5.0 (VS Code Extension)
Operating System
Windows 11
Describe the bug
The VS Code extension is unusable, it keeps crashing every time I try to use it.
It does not depend on the collection or .bru file.
It does not even work with brand new API requests.
It crashes when I just have it opened and doing nothing in it.
The error is simply "Oops! something went wrong"
The extension cannot save .bru files when I try to edit my API requests.
Click on the floppy disk shows a popup "Failed to save request".
I was fortunate enough one time to see a proper error message popup.
(I only have a partial hand copy of the message and I cannot reproduce the error popup at will, or I don't know how to reproduce the error popup)
"Unable to write file FileSystemError EINVAL invalid argument mkdir C:\file\c:" .... ( I do not have the end)
It seems to me that the path is bad because of the Windows drive letter appearing twice C:\file\c:\users or something like that. I suspect you have a mix of Windows vs Linux path somewhere.
.bru file to reproduce the bug
No response
Screenshots/Live demo link

I have checked the following:
This bug is:
Bruno version
4.5.0 (VS Code Extension)
Operating System
Windows 11
Describe the bug
The VS Code extension is unusable, it keeps crashing every time I try to use it.
It does not depend on the collection or .bru file.
It does not even work with brand new API requests.
It crashes when I just have it opened and doing nothing in it.
The error is simply "Oops! something went wrong"
The extension cannot save .bru files when I try to edit my API requests.
Click on the floppy disk shows a popup "Failed to save request".
I was fortunate enough one time to see a proper error message popup.
(I only have a partial hand copy of the message and I cannot reproduce the error popup at will, or I don't know how to reproduce the error popup)
"Unable to write file FileSystemError EINVAL invalid argument mkdir C:\file\c:" .... ( I do not have the end)
It seems to me that the path is bad because of the Windows drive letter appearing twice C:\file\c:\users or something like that. I suspect you have a mix of Windows vs Linux path somewhere.
.bru file to reproduce the bug
No response
Screenshots/Live demo link