Check the beta connection address for a bb instance and turn that connection on or off. Inspect connection states and shared port URLs, including ports exposed from other enrolled machines.
Check or switch the beta next address (https://<label>.next.getbb.app, bb connect next) for this bb.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The connect-next plugin makes this bb reachable at
https://<label>.next.getbb.app through bb's Fly gate, in addition to its
bb connect address https://<label>.getbb.app. The domain follows the bb
account it is signed in to (next.<account domain>); status prints the
exact address. It is on as soon as the
plugin is enabled and needs this bb signed in to its bb account
(bb account status).
bb connect-next status [--json] prints the label, the address, and the
state: off, signed-out, connecting, connected, refused (the gate
refused the server credential), offline (the gate can't be reached), or
error (the plugin couldn't start the tunnel; lastError says why).bb connect-next on [--json] turns it on; bb connect-next off [--json]
turns it off. Neither touches bb connect or the account sign-in.enabled, so
bb plugin config bb--connect-next set enabled true works too.Only turn it on or off when the user asks.
Port shares: every port shared from the bb server's machine with
bb connect expose <port> also answers at
https://<label>--<port>.next.<account domain> while connect next is on
(owner session only, like the bb connect share). bb connect expose prints
that URL on a second line, and bb connect-next status lists each share as
share <port> <url> <state> (--json: shares[] with port, url,
state pending | active | refused, and error).
Shares from other enrolled machines (bb connect expose <port> --host <machine>) answer at https://<machine-label>--<port>.next.<account domain>
while connect next is on; the machine's own daemon runs the tunnel while the
machine shares a port. bb connect-next status prints a
machine <name> (<host id>) <label> <state> line per machine with its
share lines (--json: machines[] with hostId, hostName, label,
state idle | connecting | connected | refused | offline | error,
lastError, and shares[]). A machine missing from the list shares nothing
or runs a bb too old for connect next machine tunnels.
The plugin itself is disabled by default: bb plugin enable bb--connect-next
first if bb connect-next is not found.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Configure and diagnose Account Pooler in BB, including accounts, authentication, quota-based routing, and failover, which switches to another account. Inspect account and routing state, plus Provider Retry decisions after pooled rate-limit failures.
Configure and troubleshoot agents connected to BB through ACP, an agent connection protocol. Manage agent discovery, registry additions, model choices, custom agent settings, skill locations, and supported conversation compaction, which condenses session context.
Approve a GitHub account to open pull requests in get-bb/bb by updating its allowlist. The workflow verifies the account, checks the change, and creates and merges an approval PR while skipping SlopCop review and CI.
Add comments to specific elements in desktop Browser tabs and include those references in prompts. Edit or delete annotation pins, or update saved comments through the plugin RPC, a command interface for plugins.
Schedule recurring or one-time BB tasks using an agent for work that needs reasoning or a server-side script for fixed checks. Manage schedules, pause and resume tasks, run them manually, and inspect execution history.
Manage the getbb.app account linked to a bb server. Check which account remote access and hosted services use, sign in through a browser or pairing code, and sign out to revoke the server's credential.