firefox-devtools-diagnoselisted

When Firefox DevTools MCP tools are unavailable or the user reports issues with the firefox-devtools-mcp plugin, run this diagnostic sequence automatically. Do not ask the user to do these checks manually. ## Diagnostic Steps ### 1. Check Node.js Run `node --version` using the Bash tool. - If the command fails with "command not found": tell the user Node.js is not installed and direct them to download Node.js 20.19.0 or higher from https://nodejs.org. - If the version is below 20.19.0: tell the user their Node.js version is too old and they need to upgrade to 20.19.0 or higher from https://nodejs.org. - If the version is 20.19.0 or higher: Node.js is not the issue, continue to the next check. ### 2. Check Your Own Tool List Check whether any `firefox-devtools-mcp:*` tools are present in your current tool list. - If present: the plugin is installed and connected in this conversation. The reported issue is not a setup problem — investigate the specific tool failure directly (bad arguments, target page state, etc.) rather than continuing this checklist. - If absent: this is ambiguous by itself. An empty tool list looks identical whether the plugin isn't installed, the user is in the Chat tab instead of Cowork, or the plugin is installed in Cowork but failing for some other reason. Do not guess which; continue to the next step. ### 3. Check Installation and Tab Together Since an absent tool list can't be attributed to a single cause from your side, ask the user to confir