Relay setup

Local CLI use does not need a relay. For remote assistants, deploy the relay/ workspace to your Cloudflare account. It uses a Worker and SQLite-backed Durable Object; no Redis, homebox, or tunnel process is needed.

Deploy

Clone the private repository using an authorized GitHub account. Authenticate Wrangler to the Cloudflare account where you want the relay to live. Edit relay/wrangler.jsonc to choose your Worker name and hostname; do not reuse another person’s deployment hostname.

cd relay
bun install --frozen-lockfile
bunx wrangler login
bunx wrangler deploy

Create two distinct random secrets with at least 32 bytes of entropy and store them in your password manager. Add DEVICE_TOKEN and CLIENT_TOKEN to the Worker using Wrangler’s secret prompt or stdin. Do not put secret values in command arguments or commit them.

bunx wrangler secret put DEVICE_TOKEN
bunx wrangler secret put CLIENT_TOKEN

The /device endpoint uses the device token. MCP uses the client token. Do not use the same token for both. Browser-oriented challenges must not be applied to this authenticated machine endpoint. Keep any Cloudflare configuration exception scoped to the relay hostname, not the entire zone.

Connect your Mac

Pass credentials from your secret manager over stdin. The accepted JSON shape is:

{
  "device_token": "YOUR_DEVICE_TOKEN",
  "mcp_url": "https://YOUR_RELAY/mcp/YOUR_CLIENT_TOKEN"
}

Pipe that JSON into:

slingring remote configure --url wss://YOUR_RELAY/device --token-stdin
slingring remote on
slingring service install
slingring status --json

When piping, connect the credential producer directly to the first command; never paste real secrets into a shell command. remote configure also accepts a raw device token on stdin, with optional --mcp-url, but credential JSON avoids exposing a secret-bearing URL in process arguments.

Connect a client

Clients supporting headers may use /mcp with Authorization: Bearer CLIENT_TOKEN. URL-only clients use /mcp/CLIENT_TOKEN and select No authentication. The URL is a capability credential, not an unauthenticated endpoint. slingring remote url | pbcopy copies the saved connection URL on macOS.

Transport behavior

The Mac initiates one outbound TLS WebSocket. A sparse heartbeat maintains connection health; it is not a job poll. The relay does not persist prompts. Offline requests fail rather than accumulating a backlog. Reconnecting never automatically resubmits a task.

The Worker authenticates both sides, checks browser Origins, bounds request size and outstanding requests, and strips URL credentials before forwarding to the Durable Object. Logs must not contain prompts or secret URLs. Disconnects and timeouts after submission are uncertain, not safe retry signals.