Supported sites

Prompt Switchboard works with the AI chat tabs you already use.

The extension is intentionally narrow. It compares supported browser chat surfaces instead of acting like a provider SDK, a hosted relay, or an automation layer for arbitrary websites.

The same boundary applies to the MCP sidecar. MCP tools can open, check, compare, retry, export, analyze, and inspect the built-in next-step workflow on these supported surfaces, but they do not become a generic website automation layer. MCP-capable local coding agents such as OpenAI Codex and Claude Code can use that sidecar surface too, but the scope remains Prompt Switchboard product actions on supported sites.

Supported today

  • ChatGPT
  • Gemini
  • Perplexity
  • Qwen
  • Grok / xAI

What to expect

  • Keep the supported site open in a normal browser tab.
  • Stay signed in with the browser session you already trust.
  • Ask once from the side panel and compare the answers locally.

What is not in scope

  • Not every AI website is supported.
  • Not every provider API is part of the product surface.
  • The MCP sidecar only exposes Prompt Switchboard product actions on supported surfaces.
  • Not arbitrary-site browser automation.

When to ask for help

  • Use Discussions for onboarding questions and support-site requests.
  • Use Issues when a supported site breaks with a reproducible bug.
  • Use SECURITY.md for sensitive reports instead of posting them in public.

Want a faster starting point after install? Use the built-in prompt packs or start from a use-case page such as rewriting, coding explanations, or local-first comparison.

Selector drift is real

Supported sites can change their DOM at any time. When that happens, Prompt Switchboard may need selector updates before the compare workflow fully recovers. Watch the latest packaged build, GitHub Discussions, and the issue tracker for recovery updates.

A site being listed here means the project is intentionally wired for that surface today. It does not mean the DOM can never change. If a supported site regresses, that is a bug to report, not a hidden fallback path.

Where to go next

Install and first run

Need the shortest path from download to first answer? Read the install guide before you load the extension.

Open install guide

Open first compare guide

Trust boundary

Want the plain-language explanation of local-first behavior and what this repository build does not add? Read the trust boundary page.

Read trust boundary

Quick answers

Need the short version for install prerequisites, support channels, or scope questions? The FAQ page is the fastest route.

Read the FAQ

Community support

New-user onboarding, workflow discussion, and support-surface questions belong in Discussions.

Open Discussions

First-run reminder

The shortest evaluation path is still the packaged release build. Keep a supported site open, stay signed in, load the extension, and compare from one side panel.