Recued Bridge
Last updated: 2026-08-20
Recued Bridge is the free browser companion for a Recued server you run and control. It lets approved recipes work with selected web pages, puts approvals and live activity in Chrome's side panel, and shows operating-system notifications from your server.
Bridge is free, and so is the server it connects to. The extension has no purchase, subscription, checkout, advertising, or Recued Pro entitlement path. It does not sell or unlock any paid Recued service, and a Recued cloud account is not required to pair it with your server. Recued's automation engine is free and self-hosted — nothing between installing Bridge and running your first recipe asks you to pay.
Recued does offer an optional paid convenience for people who would rather not run their own DNS and certificates. Bridge neither promotes it, links to it, nor behaves differently with or without it.
- Your server — You choose and pair the Recued server Bridge connects to.
- Your websites — Bridge starts with no website access. Chrome asks before granting access to a site.
- Your approval — Browser actions come from the server and recipes you control, within permissions you granted.
- Your data — Recipe execution and connected-service credentials remain on your server. Bridge keeps only the local state needed to operate.
What Bridge does
- Carries out supported browser steps requested by an approved Recued recipe, such as reading a field, filling a form, clicking an element, or capturing a selected page when the action requires it.
- Shows paired-server health, active work, recent runs, notifications, and pending approvals in Chrome's side panel.
- Lets you approve or reject a pending action without leaving the page.
- Lets you select a page element and send its selector to your server to create a watch.
- Shows user-visible desktop notifications requested by your Recued workflows.
Bridge is a thin actuator, not the automation engine. It does not execute recipes, store your warehouse, hold connected-service credentials, or route traffic through Recued's cloud.
Pairing and site access
A self-hosted Recued server is required, and it is free to install and run. Pairing uses the server URL and the one-time pairing details created by that server. Those details connect Bridge directly to the server you selected; they are not a Recued cloud login, and creating them costs nothing.
The extension ships with empty default host permissions. When an approved action needs a website, Bridge asks Chrome for access to that origin. You can deny the request or revoke access later in Chrome's extension settings.
Chrome permissions
| Permission | Why Bridge uses it |
|---|---|
storage | Store local settings, pairing state, queues, and wrapped token material. |
alarms | Run keepalive, retry, and maintenance work for the extension service worker. |
notifications | Show user-visible notifications requested by your workflows. |
tabs | Find the active or relevant tab for an approved browser action. |
scripting | Run a supported action or the element picker on a site you granted. |
sidePanel | Provide Bridge status, activity, notifications, approvals, and controls. |
| Optional website access | Ask for a specific HTTP or HTTPS origin only when it is needed. |
Bridge does not request default access to every website. It does not request Chrome permissions for cookies, bookmarks, web-request interception, desktop capture, proxy control, VPN control, or browser debugging.
Why Chrome says "Read your browsing history"
When you install Bridge, Chrome warns that it can read your browsing history. That wording is Chrome's, and it is triggered by the tabs permission — the same warning appears for every extension that can see the address of an open tab.
What tabs actually allows is reading the URL and title of tabs that are open right now, which Bridge uses to find the tab an approved action refers to and to confirm it matches an origin you granted. Bridge does not request Chrome's history permission, so it cannot read the pages you visited yesterday, search your history, or see anything after a tab is closed. Nothing about your browsing is sent anywhere except the specific page data a recipe you approved asks for, and that goes only to your own server.
Data and privacy
Bridge stores its settings and pairing state in Chrome extension storage and IndexedDB. Page content, selected URLs, form values, selectors, or screenshots are handled only when a user-authorized recipe or Bridge action needs them on a site Chrome has allowed. The result goes to the paired server.
Bridge does not sell data, use data for advertising, or load remotely hosted executable code. See the Privacy Policy for the complete data-use disclosures, and the Bridge Terms for the terms that apply when you install it — including the Chrome Web Store Limited Use commitments and the prohibited-permission list.
Availability and help
The Chrome Web Store release is being prepared for review. Once the listing is approved, this page will link directly to the store installation page.
For pairing, permissions, or review questions, see Support or email support@recued.com. To install and run the required server, start with Get started. Installing Bridge is covered by the Bridge Terms.