Connected to local bridge

Saved taps run in this browser. Credentials stay on your machine.

Setup required

Register the native messaging manifest:

    tap bridge setup

One-time. The extension ID is pinned in the manifest, so the command takes no flag — copy & run.

Don't have Tap installed?
Bridge not running

The bridge launches when this extension's service worker is active. Try:

- Make sure Chrome's window is open — closing all windows suspends the SW.
- Click the Retry button below to wake the SW + relaunch the host.
- If it persists, the host may have crashed — open `host.log` next to your `tap` binary (find it with `which tap`); the last lines say why.

Learn more
Chrome blocked the host

Either Chrome's anti-DoS lockout is active (~10 min), or the manifest's `allowed_origins` is wrong. Re-register:

    tap bridge setup

- Fully quit Chrome (⌘Q) and re-open — this clears the anti-DoS blocklist.
- Then click Retry connection.

Learn more
Bridge in use by another profile

Tap runs one bridge per machine, and another Chrome profile is holding it right now. This profile can't use the bridge until that one releases it.

- Use Tap in the profile that owns the bridge, or close it / disable the Tap extension there.
- Then click Retry connection here to take over.

Learn more
Bridge down

Reason: `—`

Run the diagnostic — it prints which side is unhappy:

    tap bridge status

Learn more