VS Code Language Server and Linter Setup Troubleshooting Guide
Diagnose why completion, errors or formatting do not work.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me troubleshoot my VS Code language support. Language and extensions installed: [LANGUAGE_AND_EXTENSIONS]. What is not working (for example no completion, wrong errors, formatter ignored): [SYMPTOMS]. Operating system and project structure: [SYSTEM_AND_STRUCTURE]. Output panel messages, with secrets and private paths removed: [OUTPUT_MESSAGES]. Change one thing at a time and record the result. Diagnose in order of likelihood and cost to check, giving the exact place to look [VERIFY menu names] and what a good result looks like: the correct interpreter or runtime selected, the workspace folder opened at the right level, configuration files present and valid, conflicting extensions, a formatter set as default, trust settings, and extension logs. Clean test: open an empty folder with a minimal file and see whether the feature works there. Reset procedure that does not destroy settings: disable extensions one at a time, and use a new profile and compare [VERIFY]. List what to include when asking colleagues for help, and warn against pasting private paths or tokens from logs.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.