Browser Extension
The Bifurc Companion extension connects your browser directly to Bifurc for proxy control, capture-driven workflows, and quick creation of requests and mocks from live traffic.
What it does#
The extension provides three main capabilities:
- Proxy toggle from the browser — route traffic through Bifurc without opening OS proxy settings.
- Companion bridge — a localhost WebSocket bridge for sending actions into the desktop app.
- DevTools workflows — capture network activity and turn it into Bifurc entities.
Installation#
Chrome Web Store (Recommended)#
Install the Bifurc Companion extension directly from the Chrome Web Store.
Firefox Add-ons#
Install the Bifurc Companion add-on from Firefox Add-ons.
Load unpacked#
- Open
chrome://extensions - Enable Developer mode
- Click Load unpacked
- Select the
bifurc-extensionfolder
Browser support#
- Chrome: supported
- Firefox: supported
- Other Chromium browsers: likely compatible if they support the required APIs
Popup workflow#
Open the extension popup to control the browser-to-Bifurc connection.
Configure ports#
The popup stores:
- Proxy port — the Bifurc forward proxy port (default 8080) that should receive browser traffic
- Companion port — the localhost WebSocket bridge port Bifurc listens on
These values should match the desktop app settings for your current workspace setup.
Enable proxy routing#
Send browser traffic through Bifurc with the extensionVideo coming soon
When you enable the proxy toggle, the extension writes a PAC configuration through the browser proxy API so traffic is routed through 127.0.0.1:<proxyPort>.
That gives you a fast on/off switch for:
- capture sessions
- mock interception
- proxy-rule testing
- browser validation against mapped services
HTTPS without the certificate#
With the toggle on, mocks, proxy rules and capture also work for the HTTPS calls a page makes, with no certificate to install and HTTPS interception left off. Nothing changes in how you use it: the same toggle, and the calls show up in Capture like any other, live streams included, ready to save as a request or a mock or to add to a flow.
The extension catches a page's fetch, XMLHttpRequest, EventSource and WebSocket calls before the browser encrypts them and asks Bifurc what to do with each one:
| Bifurc finds | What happens |
|---|---|
| A mock that matches | The page gets the mock's answer. Nothing goes to the network |
| A proxy rule that matches | Bifurc sends the call to the rule's target, runs the rule's scripts and fills in vault secrets, and the answer streams back to the page. A local server behind a production URL works as it does with the certificate: it gets the request in plain HTTP with the production Host |
| Nothing | The browser sends the call itself, with its own cookies, HTTP/2 and streaming, and the extension reports what came back to Capture |
Cookies keep working through rules: the extension sends the browser's cookies for the request, and stores what the rule's target sets.
What still needs the certificate#
The extension only sees calls a page's scripts make. These go straight to the network over HTTPS, unmocked and uncaptured, unless you install and trust the Bifurc CA and turn on HTTPS interception:
- page loads and navigations
<img>,<script>, stylesheets, fonts and other resources the page loads itself- requests made by service workers and web workers
- synchronous
XMLHttpRequestandkeepaliverequests, such asnavigator.sendBeacon - anything that is not a browser, such as your backend, a CLI or a mobile app
When HTTPS interception is on and the certificate is loaded, the extension stays out of the way and Bifurc's proxy handles HTTPS as before, so nothing is captured twice. Plain http:// traffic always goes through the proxy.
DevTools workflows#
Open DevTools and switch to the Bifurc tab.
Capture and review#
The panel records browser network activity and shows:
- request method
- URL
- status
- asset type
- size
- timing
Save a request to Bifurc#
- Open the Bifurc DevTools tab
- Trigger traffic in the page
- Find a captured row
- Click Save
- The extension sends the request to the Bifurc companion bridge
- Bifurc creates a saved request in the active workspace
Turn traffic into a mock#
- Capture a request in DevTools
- Click Mock
- The request and response payload are sent through the companion bridge
- Bifurc creates a mock prefilled with:
- method
- URL pattern
- request headers and body
- response status, headers, and body
Bulk-create mocks or requests#
The DevTools panel also supports batch workflows over the current filtered view:
- create a folder
- send multiple captured requests as mocks
- send multiple captured requests as saved requests
This is useful when reverse-engineering an existing frontend API surface quickly.
Context-menu workflow#
The extension adds browser context-menu actions:
- Mock this request [Bifurc]
- Add to Requests [Bifurc]
These are quick helpers for link-driven workflows and feed actions into the same companion bridge.
Companion bridge details#
The extension talks to Bifurc over a localhost WebSocket connection:
- default companion bridge:
ws://127.0.0.1:4747 - reconnects automatically with backoff
- never sends traffic to external servers
Open Settings, under Servers, to see which browser extensions are currently connected to the app. Each one is listed with its browser and operating system, which is the quickest way to tell whether the extension has reached the right Bifurc.
The bridge is intended for additive actions such as:
- creating requests
- creating mocks
- creating folders for captured items
Security model#
- Communication is localhost-only
- The extension does not send data to a cloud backend
- Proxy routing is browser-scoped through browser APIs
- A page's HTTPS calls are routed through Bifurc by the extension without a certificate. Rules run inside Bifurc, so vault secrets never reach the browser
- Everything else over HTTPS (page loads, other resources, workers, non-browser clients) still needs the Bifurc CA trusted in the desktop app
Current scope and limitations#
| Capability | Status | Notes |
|---|---|---|
| Proxy toggle | Supported | Configurable through popup |
| DevTools capture | Supported | Best for browser HTTP traffic |
| Save captured traffic as request | Supported | Uses companion bridge |
| Save captured traffic as mock | Supported | Includes response payload when available |
| Bulk save/mock | Supported | Based on current filtered DevTools view |
| HTTPS mocks, rules and capture without the certificate | Supported | A page's fetch, XHR, EventSource and WebSocket calls; see HTTPS without the certificate |
| WebSocket and SSE capture | Supported | Messages appear live in Capture |
| gRPC capture | Not provided by extension | gRPC uses HTTP/2 framing outside this workflow |
Troubleshooting#
| Issue | What to check |
|---|---|
| Extension shows disconnected | Confirm Bifurc is running and the companion port matches. Settings → Servers lists the companions that are connected |
| Browser traffic is not captured | Confirm proxy routing is enabled and the proxy port matches Bifurc |
| A page's HTTPS calls are not mocked or captured | Confirm the toggle is on and Settings → Servers lists the extension. Calls made by service workers and page loads need the Bifurc CA |
| HTTPS sites fail with HTTPS interception on | Generate, install, and trust the Bifurc CA |
| DevTools panel appears stale after reload | Close and reopen DevTools after extension reloads |