When browser proxy extensions fight with Clash
A browser extension's proxy setting takes precedence over the system proxy — the extension wins. Hence two classes of spookiness: Clash is on and node switches do nothing (the extension routes elsewhere); or Clash has quit and the browser still spins (the extension points at a dead port).
Pick one — recommended options
- Option A (recommended): remove/disable the proxy extension and let the browser follow the system proxy. Clash already does rule-based routing in the core; the browser does not need a second router. Best answer for most people;
- Option B (keep the extension): if you genuinely switch per-site/per-tab by hand, point the extension's proxy scenario at Clash (127.0.0.1:7890) and set its default scenario to "system proxy" — making the extension a front end for Clash rather than a rival.
Untangling an existing mess
- Extension icon → switch to "direct connection"; confirm the browser reaches local sites;
- Switch to "system proxy"; confirm access through Clash works;
- Audit the extension's stored ports (an old 1080 from years ago?) and delete dead entries.
To know who is really carrying the traffic: if the connection shows up on Clash's Connections page, it went through Clash; if not, the extension sent it elsewhere.