Platform · VS Code
VS Code Fixes
Copy-paste fixes for the VS Code problems that interrupt your work. Extensions, settings, and the errors that make you close the editor and try again.
Why these pages exist: VS Code has 60,000+ extensions and 100+ settings. When something breaks, the answer is buried in a GitHub issue or a 30-minute YouTube video. We give you the fix in 30 seconds.
🚨 Fix Pages
Something broke. Here's how to make it work again.
Two extensions fighting, editor acts weird
Fix: VS Code Extension Conflict
Autocomplete is broken, formatting fights itself, or IntelliSense stopped. Two extensions are fighting. Find out which.
Changed settings.json. Nothing changed.
Fix: Settings Not Applying
You edited settings, saved, reopened — and your changes aren't taking effect. It's usually workspace vs user settings, or a JSON syntax error.
No autocomplete, no error highlighting
Fix: IntelliSense Not Working
Autocomplete stopped suggesting. Go-to-definition doesn't work. Usually a language server crash or workspace config issue.
Extension installed but not activating
Fix: Extension Won't Load
Installed the extension, it's showing as enabled, but its commands don't exist. Extension host may be crashing.
🚧 More Coming
Growing section. Here's what's next.
Slow editor, laggy typing
Fix: VS Code Running Slow
Extension audit, process explorer, and the settings that matter.
Terminal not opening / broken
Fix: Integrated Terminal Issues
Default shell, profile config, and the common PowerShell/Zsh problems.
Git commands not working
Fix: Git Integration Broken
Git detection, path issues, and rebasing the source control panel.
📖 How to use these pages
1
Match the symptom
You don't need to know which extension is broken. Find the page that matches what you're seeing.
2
Read the 30-second fix
Every page opens with the fastest safe answer.
3
Check the "commands" section
Most VS Code fixes can be run from the Command Palette (Ctrl+Shift+P). Each page lists the exact commands.