I am using my Windows machine that uses WSL and my entire project is ran inside a docker container. Previously, I would run docker desktop, open up vscode and have it reopen inside my dev container.

I have been using Tidewave everyday since your initial post a couple weeks ago and have had no issues at all (it’s mind blowing to me especially because it is my first taste using an agent), but I believe I woke up yesterday to start everything like normal except Tidewave is no longer able to read/write any of my project files, suggesting that my project isn’t mounted in the container.

Between claude, myself, tidewave, and chatgpt I can not for the life of me figure out how to get back the flow I have had the last week or so. I have noticed that the settings have been updating very frequently, but one thing I noted was yesterday morning the editor integration section started assuming I was using windows UNC paths when my files were in linux so as of yesterday morning the vscode integration tries to open my README with opposite formating so I had to use the custom path helper at the bottom. Don’t know if it is related to not being able to see the project files.

My next step is deleting everything from this machine and starting over. I have the project in git, but I’m on hour 9 or 10 trying to get this working again.

That being said, this is hands down the best thing I’ve used in the last 10 years.

I suspect this is an issue with me setting up Docker and my environments, not any changes in Tidewave, by the way.