Extension Conflict Detector is your personal anti-chaos tool for Visual Studio Code. It automatically scans your installed extensions, detects duplicate functionality, and flags conflicting keybindings — keeping your dev environment clean and predictable.
Features
🧩 Smart Detection: Finds duplicate formatters (Prettier vs ESLint), language servers (LSP), and linters.
⌨️ Keybinding Guard: Catches keybinding conflicts so the same shortcut doesn't trigger different actions across plugins.
🔧 One-Click Resolution: A built-in control panel with quick access to settings and one-click disabling of conflicting extensions.
📡 Real-Time Monitoring: A live badge counter on the sidebar icon shows the number of active conflicts at a glance.
How to Use
Installation
Find Extension Conflict Detector in the VS Code Marketplace and click Install.
Getting Started
After installation, a new icon appears in your Activity Bar.
Click it to open the Conflict Detector panel.
The extension automatically scans all installed plugins and displays results as interactive cards.
Resolving Conflicts
View Details: Each card has a Details button — see the conflict description and a recommended fix.
Disable Extension: Click Disable [Extension Name] to open that extension's Marketplace page, then disable it in one click.
Reload: After disabling, reload the window (Developer: Reload Window) for changes to take effect.
Due to VS Code security restrictions, extensions cannot disable other extensions directly. The button opens the relevant page so you can do it manually.
Supported Conflict Types
Type
Description
⚠️ Double Formatter
Multiple plugins attempting to format the same language simultaneously.
⚠️ Double LSP
Multiple autocompletion servers for one language (e.g., Pylance + Python).
⚠️ Duplicate Linter
Multiple linters checking the same code, creating noise in the Problems panel.
⌨️ Keybinding Conflict
Two different actions assigned to the same keyboard shortcut.
FAQ
Why is there a red number on the icon?
That's your active conflict counter — it shows how many problematic extensions are detected right now.
Does this slow down VS Code?
No. Scanning happens lazily when you open the panel. Background resource usage is minimal.
Can I ignore specific conflicts?
The current version automatically filters out built-in Microsoft extensions. To exclude something specific, use the Disable button to temporarily remove it from the active set.
