---
name: get-bb-share-server-links
description: "Expose a local HTTP server through BB Connect and give the user its remotely accessible URL."
license: "MIT"
metadata:
  decimalai-skill-id: "330ea34b-3f81-4ff6-9218-0bbaa97ea0e0"
  decimalai-version-id: "9c970f27-bec9-41a8-94cd-7176e0b9018c"
  decimalai-version: "3"
  decimalai-body-sha256: "0d960253e53f768ad203b574d51b0ac2fd5b1d1d9bc90569b2452c6dbc845c14"
  decimalai-name: "get-bb/share-server-links"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/get-bb-share-server-links@3/SKILL.md"
---
# Share local server links via bb connect

When you start an HTTP server the user should open, give them a connect share
URL — not a localhost URL. Shares work from threads running on any enrolled
host, and the command resolves the thread's host automatically.

1. Check pairing: run `bb connect status --json`. If not paired / not
   connected, give the localhost URL and mention that `bb connect` enables
   remote URLs once paired from the getbb.app dashboard.
2. From the thread that started the HTTP server, run `bb connect expose
<port>`. It prints that host's share URL. Use `--host <name-or-id>` only
   when you intentionally need another enrolled host; outside a thread,
   sharing defaults to the machine running the bb server.
3. Give the returned URL to the user as a markdown link. It works for viewers
   who have the owner's getbb.app session; it is not a public internet link.
4. When the server stops, run `bb connect unexpose <port>` from the same
   thread (or with the same `--host`) so the share is cleaned up. Use
   `bb connect shares [--host <name-or-id>]` to inspect that host's shares.

`bb connect --help` and `bb connect <command> --help` print the commands and
their flags and exit 0. Unknown commands and flags fail with a suggestion —
`bb connect list` points at `bb connect shares` — and with `--json` a failure
prints `{"ok":false,"error":{"code":…,"message":…}}` on stdout while the same
message stays on stderr.

Server-host shares use `https://<server-label>--<port>.<base-domain>` through
the server tunnel. Other enrolled hosts use
`https://<machine-label>--<port>.<base-domain>` through their daemon. If a
machine was not enrolled through Connect, expose fails with instructions to
remove and re-add it under Settings > Machines.

## Agent instructions setting

Settings → Installed plugins → Connect has a "Tell agents about remote access"
toggle, enabled by default. Use
`bb plugin config connect set sendRemoteInstructions false` to suppress the
remote-access message, or `true` to restore it. This controls only the message;
sharing still works. The message otherwise requires active or recent remote
usage. Changes apply when session instructions are next assembled.