Setup · 0.7.3

Connect Bridgefold.

Connect an OpenAI-compatible API directly from the extension. No native host, Node.js or Cursor installation is needed for this path. Install the current public release from the Chrome Web Store. Staged candidate 0.7.3 is separate from the published release; staging alone does not publish an update.

1. Connect your AI provider

1. Open Bridgefold beside a harmless webpage and choose Use an API key.
2. Select OpenAI or OpenRouter and paste your API key. The endpoint and model are filled in. Advanced offers a model/name override; Other provider requires an OpenAI-compatible HTTPS API URL and model ID. The model must support tools, tool results and image input.
3. Allow the exact provider origin when Chrome asks. Connecting checks the model list and sends up to two short compatibility test completions with built-in data, including a tiny image. It may use API credit; it does not read your page.

Your key is encrypted in this Chrome profile and restored after restart until Disconnect/Forget. Trusted extension code can decrypt it; this is not an OS keychain or protection against a compromised profile. Provider policies, charges and limits apply. HTTP endpoints, including localhost, are not supported by this browser API path.

2. Try a task

Choose Read only, review the disclosure and select Accept and continue. Ask for a one-sentence summary and compare it with the actual page. Prompts and selected page content go directly from the extension to the chosen API endpoint. Chrome shows its debugger warning during page inspection/control. See Privacy for data, storage and recipients.

Browser chat history is bounded locally. Closing or reloading the panel interrupts a task; reopening never silently resumes actions. A new provider connection cannot inherit an old chat's context. Routines, memory, MCP, cloud and Continue in Cursor are unavailable in browser API mode.

Try a demo

This labelled local walkthrough needs no account and uses scripted replies. It cannot read real pages or prove AI access. Demo chats and automation drafts last until reload or exit.

Troubleshooting API connections

• Access denied: allow the provider's exact HTTPS origin, then connect again.
• Could not connect: check the endpoint, model, key, provider balance and tool/image support. A successful model list does not establish chat access.
• Browser restarted: the saved connection is restored without re-entering the key. If you used Disconnect/Forget, connect again. Old history stays local; tasks never silently resume.
• Task interrupted: reopen the panel on the intended page and start a new task. Nothing is silently replayed.

Optional Cursor native connection — qualification pending

Choose Connect with Cursor to see its available sign-in methods. Back returns to the main connection choices. This separate native path needs both the extension and native host com.bridgefold.host. Public IDE companion/bootstrap and automatic installation are not qualified for this candidate. Installing the extension alone does not install the Cursor native integration.

Native qualification targets are macOS arm64 and Linux x64. Windows DPAPI exists in the code, but Windows native distribution is deferred. Native isolated accounts need macOS Keychain or Linux libsecret and an available Secret Service. These constraints do not apply to browser API tasks.

The native candidate needs a compatible runtime with SQLite and FTS5 unless its exact qualified archive bundles one. Do not assume a proposed bundle is shipped. Unsigned macOS archives may invoke Gatekeeper checks; keep OS protections enabled. Native cloud tasks require suitable Cursor browser sign-in.

Native downloads and installation commands are withheld here until exact artifacts and clean-machine lifecycle checks are qualified. Developers can use the repository's native setup documentation; the Store extension ID is ldaokpboecinjokbdlnjcmgnkaemmnjc.

Review walkthrough

1. Use a clean Chrome profile with the extension and the private review API details; no host or Node is needed for API mode.
2. Connect and grant the provider origin, then accept the task disclosure. Summarize https://example.com/ and compare the response with the page.
3. On a disposable form, approve one reversible edit and verify the real page change. Deny another action and confirm it is not executed.
4. Use Pick element; Escape cancels it. Stop a multi-step task and verify further actions cease.
5. Close/reload the panel and check interruption. Restart Chrome and check that the saved connection is restored without re-entering the key or replaying a task. Then Disconnect/Forget and confirm the credential does not return after restart.

Private reviewer access, real provider usage and clean-machine qualification remain separate release gates. Native candidate artifacts must be qualified before this page offers them. Need help? Support or the.career.odyssey@gmail.com. Terms.