Install the latest build and send your first compare prompt.
This is the shortest path to a real product trial. You do not need to build the project locally to evaluate Prompt Switchboard.
Before you start, keep the supported AI tabs you want to compare already open and signed in inside the same browser profile where you load the extension.
Once the side panel opens, use the built-in first-run checklist to open tabs, refresh readiness, and seed the first compare prompt without bouncing back into the docs.
If you want the shortest operator-style map from “extension installed” to “first compare run really succeeded,” use the first compare guide. It keeps the first-run checklist, repair ladder, and login-gated explanation in one place.
When a compare turn finishes, the built-in next-step workflow can either stage the next prompt or run the next compare again. Seed-only actions stay explicit so the product does not pretend a prepared prompt has already executed.
When the first compare run is done, you can keep moving inside the same workflow: copy a compare summary, export Markdown, or load one of the built-in prompt packs without rebuilding the task from scratch.
Optional AI analysis is now available too, but it runs through a browser tab you already keep signed in. The default compare workflow still works without any separate provider or hosted relay.
There is also an optional local MCP sidecar for agent integrations. It is not required for the first compare run, and it does not replace the default compare workflow. If your local coding agent speaks MCP, Prompt Switchboard can expose compare, retry, export, analysis, and built-in next-step workflow actions there without turning into generic browser automation. In practice the main documented builder bindings are OpenAI Codex and Claude Code, while the MCP agents page covers the fuller repo-local operator helper path.
The supported install path today is the packaged GitHub Release zip. Browser-store submission materials are being kept ready, but GitHub Releases remains the supported install surface today.
What you need first
- A Chromium-compatible browser with Developer Mode available
- At least one supported AI chat tab already open and signed in
- A local folder where you can unzip the packaged release
Quick install path
- Download the latest packaged release zip and unzip it locally.
-
Load the extracted folder in
chrome://extensionsas an unpacked extension. - Open your supported AI tabs, then ask once from the side panel.
Current distribution surface
Today the supported path is the packaged release zip from GitHub Releases. A lower-friction browser-store path is being prepared, but it is not live yet.
Permission footprint
sidePanelkeeps the compare workspace inside the browseractiveTab,scripting, andtabslet the extension drive supported AI tabsstoragekeeps sessions, settings, and selector cache local-firsthttp://127.0.0.1:48123/*is reserved for the optional local MCP bridge- Host access is limited to supported AI chat surfaces and optional selector updates