Another vs code headache · AI Automation Society

Another vs code headache

so. how are people dealing with this issue, that vscode seems to:

Always write to c(lower case) and not C(upper case) file location, & searches for existing in the same fashion.

regularly causing issues with "mcp not found" or other such things,
sending claude into a spiral of context & token waste trying to solve a problem that it never will without you specifically telling it whats wrong.

Powershell or Cli however, always use C (with a capital), and alot of the time, claude will automatically run one of these mid solution if i set it to solve something without me. creating two unreconcilable branches.

maybe you havent noticed it, because if you have something installed or implemented at ~user for global install, it never has to go through the full file path that uses c or C.

meaning global installs are immune to this. it only happens in project specific installs

ive noticed Nate doesnt have these issues when hes installing mcp's in his project. it just works directly for him, which makes me wonder what im missing.

he is definitely doing something to solve this issue directly. but i don't think hes posted anything about it.

i know many people will encounter this problem, so i could really use some help. - its killing all my skills and self healing

19 comments

Another vs code headache