get-bb 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.
- Check pairing: run
bb connect status --json. If not paired / not connected, give the localhost URL and mention thatbb connectenables remote URLs once paired from the getbb.app dashboard. - From the thread that started the HTTP server, run `bb connect expose
. It prints that host's share URL. Use --host 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, runbb connect unexpose from the same thread (or with the same--host) so the share is cleaned up. Use bb connect shares [--host ]` to inspect that host's shares.
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.