Hi,
I’ve installed the new “Work with Apps” VS Code extension (Following these steps: https://help.openai.com/en/articles/10128592-how-to-install-the-work-with-apps-visual-studio-code-extension)
But then I get an error in VS Code:
The ChatGPT extension cannot find its registration file
And regardless how many times i click “Reregister” it keeps coming up.
Has anyone had this issue before?
My VS Code version:
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.0.0
ChatGPT App version:
Version 1.2024.310 (1731435581)
I think because of the error mentioned in the first post, i’m unable to hook into an existing workspace:
i’m on the same page 
i can’t find any solution yet
FWIW, I had the same issue using VS Code Insiders. I did a clean install of VS Code (non-Insiders) and installed the extension and the error is gone.
Maybe a conflict with other extensions I had, maybe an issue with VS Code Insiders itself.
Weirdly, the “No workspaces available” error only shows up when i have a workspace or folder open. If i have an emptyVS Code window open, i can select “Code” in ChatGPT app…
Same thing happens to me.
The problem is that even if you get it to “connect” and the thing goes green (which I also managed to do later), it is not getting any of the selection data from VS Code.
I’ve tried uninstalling the extension entirely, disabling the feature in the ChatGPT macOS app, restarting both apps, redownloading the extension, reinstalling the extension, and reenabling the “Work with Apps” feature, all to no avail. While i can get it to show as “paired”, it still is not getting any selection data - unlike what happens when I use TextEdit or Terminal.
Also, when I go to Settings > Work with Apps > Manage Apps in the ChatGPT app, Code shows up there with “Extension needs update”, and clicking “Update Extension” jumps into Code and opens the extension’s property page (where I’ve also checked the “Auto-update” box, by the way).
I’ve submitted a bug report with screenshots ~12 hours ago, so hopefully between this thread and bug reports from people, OpenAI will sort this out soon. Just before posting this here, I redownloaded the extension from the help article link to see if it’s been updated, but it’s bit-identical to the one I downloaded yesterday.
Piling on here. Having the same issue.
(post deleted by author)
Potential solution here: [Visual Studio Code] PHP BUG with "Work with Apps" on macOS?
Looks like openai staff has eyes on it. Hopefully a patch will be out soon! 
Thanks for referencing that zenz - I was indeed able to get rid of the issue with info from that thread.
TL;DR, basically if you have a workspace or folder that’s open that has a period in its name, this bug will rear its ugly head. Closing the folder/workspace and either opening individual files, or opening a folder that doesn’t have a period in its name fixes the problem (and so does closing the folder and renaming it to remove the period - though had to do it via Terminal, as my Finder didn’t seem to want to remove the period directly).
Also, the Reregister message goes away and doesn’t come back unless you try to open a folder with a period in its name again.
(In ChatGPT app Settings > Work with Apps > Manage Apps it still says extension needs updating, but not too concerned about that as long as the feature is working correctly.)
Thanks. So it sounds like a bug that needs to be fixed All my folders have either a dash or a period in them lol)
also using the VS Code Insiders build here and unfortunately the extension doesnt work this way.
I believe we need to support VS Code Insiders
I am using regular VS Code. Still same issue so it is not an insiders related bug.
Does anyone know how to elevate this? They showed this at their dev day today which should increase the blast radius of this. Being able to parse a folder name with a “.” should be an easy enough fix.
No idea, but here we are in a new year 
hopefully something that would be fixed soon. Surely we’ll be out of beta soon!
I have the same issue, @OpenAI_Support can you please have a look or give some place to track the progress
