[Visual Studio Code] ".com in Folder" BUG with "Work with Apps" on macOS?

[0x1337]

Hello everyone!

I jumped on this amazing new feature (Work with Apps on macOS) in beta.

I followed the guides thoroughly:

https://help.openai.com/en/articles/10119604-work-with-apps-on-macos

For Visual Studio Code:

https://help.openai.com/en/articles/10128592-how-to-install-the-work-with-apps-visual-studio-code-extension

iTerm 2 works perfectly, but I can’t get Visual Studio Code to work with ChatGPT…

I’ve reinstalled the extension dozens of times, restarted Visual Studio Code, ChatGPT, and my MacBook Pro M1.

I’ve unchecked and rechecked the Mac’s Privacy settings, and even added Visual Studio Code to the Privacy settings (just in case).

But nothing works,

I can’t sync VS Code with ChatGPT

Has anyone experienced this issue or solved it before?

Thanks in advance!

After try and try and try its strange but it’s working if I open html folder:

But not working if i open my php folder:

Redirect me on extension …

[0x1337]

I found the problem !

I thing bug is because I open Folder with “.com” in filename !
Exemple: “server-domain.com”

My project work perfectly but my folder name is “projectname.com” and I have configuration in NGINX for this.

I thing OpenAI need to be update Visual Studio Code Extension about this problem ?

Any can report this bug please ?

Thanks a lot

[jn-opeani]

Glad you found the issue!

I’ll look into the .com issue in the workspace name. Thank you for reporting.

[zenz]

Confirmed. If I switch to a project that does not have .com in the workspace folder name, it works for me.

User journey: I map remotely via ssh, and I (and apparently many others) often structure apache/nginx/etc. roots using the domain.

[pom.pom.tom]

Not just a .com in the folder name — even just a period in the folder name will recreate the issue — just confirmed on my end.

If I open a folder with no periods in its name — no issue. If I then close the folder in VScode, rename it so it has a period somewhere in the middle of it, and then reopen the folder in VScode, I get the issue. If I close it, rename back, then reopen, issue is gone again.

Basically, seems like it’s a problem with the folder/workspace having a period in it, and the extension doesn’t like that.

[0x1337]

Hello
Bug is not fixed since this time
When fix please ?