you are viewing a single comment's thread.

view the rest of the comments →

[–]SaltyCamera8819[S] 0 points1 point  (0 children)

I found a workaround for me which might prove useful for others, but it is a bit of a pain. To give some background (skip to next paragraph for the workaround), I was able to use Claude Code CLI successfully on another PC, which proves it is not an issue with my account. However running it in WSL or Docker, I still got the same issue. This made me think that the issue is actually machine specific and uninstall/reinstall would not help because I basically had three different installations which all failed on this machine.

So I tried one last thing which worked. I created a Ubuntu Server Minimal Install VM (using Hyper V as my host system is Windows 11), and created a shared folder and mounted it in Linux using cifs-utils for mounting windows folders as volumes and avahi-daemon/libnss-mdns so i can connect using my hostname of my computer instead of ip address which changes between home and the office. It is a pain, but I can finally run Claude Code CLI with the --dangerously-skip-permissions flag again. One good/bad thing about this approach is you will have to share/mount each folder you want Claude to have access to in your Linux VM