# Install BridgeSwarm

TabBot cannot log a discord.js `Client` in with Chrome alone. Discord’s REST and Gateway are not CORS-open to `http://127.0.0.1:5173`. The Client lives in BridgeSwarm’s **Bare native host**. The extension is the bridge from this origin to that host.

## macOS / Linux

```bash
curl -fsSL https://install-bridgeswarm.honeypeer.com | bash
```

## Windows (PowerShell)

```powershell
irm https://git.ssh.surf/snxraven/BridgeSwarm/raw/branch/main/scripts/install.ps1 | iex
```

## After the installer

1. **Fully quit the browser** (all windows). Extensions and native messaging do not attach to an already-running Chrome/Chromium/Edge session reliably.
2. Reopen the browser and confirm the BridgeSwarm extension is enabled.
3. Host files live in `~/.bridgeswarm/` (macOS/Linux) or `%LOCALAPPDATA%\bridgeswarm\` (Windows). That tree is **not** the TabBot vault.
4. Continue with [Enable Discord pack + allowlist](/docs/guide/enable-discord).

## If install failed

- Native host not registered: re-run the installer, then quit the browser again.
- Extension missing: load it from the BridgeSwarm distribution the installer printed.
- Policy-locked browsers (some managed Chromebooks / enterprise Edge) cannot load unpacked native messaging. Use a browser you control.

BridgeSwarm is a **separate AGPL-3.0** program. TabBot does not vendor or relicense it. Canonical Discord notes: [BridgeSwarm DISCORD.md](https://git.ssh.surf/snxraven/BridgeSwarm/src/branch/main/docs/DISCORD.md). TabBot itself is GNU GPL v3 or later at [git.ssh.surf/snxraven/tab-bot](https://git.ssh.surf/snxraven/tab-bot). Stuck? [Community](/docs/guide/community).