BB plugins

I keep a few threads as permanent managers, one per area, like this site or a product. A manager keeps its area’s context and doesn’t do the work itself: it starts an ordinary subthread for each task, checks what comes back and archives the subthread when the task is done. Those roles and rules are my own setup on top of BB. The plugin doesn’t install or run them.

Responsibilities shows where that tree needs you. A red ✕ means a thread failed, an amber ? that it waits for your answer or approval, and a dot that it has a result you haven’t seen, in subthreads too. A collapsed parent shows the failures and dots below it, plus counts of descendants working, waiting or failed. Put your managers’ thread IDs in a JSON file to make them bold and give them a filter; Needs you keeps only the marked threads and their parents. New child thread starts a subthread under any thread, with Full Access preselected, so check the mode before you send. Records stay in local SQLite, with no telemetry.

Turn on Compact warm theme in the plugin settings for warmer colors, tighter rows and nesting, and guides along the selected or hovered branch. Row actions appear over the title when you need them, leaving more room for its name. The theme is off by default; turning it off restores your BB theme while keeping the marks and filters. Touch screens keep larger row targets.

Open a thread, and each descendant that needs you opens beside it as a column, however deep it sits. A column goes to a subthread that waits for your answer or approval, or has failed; with Responsibilities, also to one with a result you haven’t read. Subthreads that are working or have nothing new get no column, but they still show in the path above a column’s title. Each column has its own composer, so you answer in place. Beside your thread it shows up to 8 subthread columns by default, then +N more.

Each thread starts with a model letter: A for GPT-6-Astra, O for Opus. Small strokes below it show effort: one for High, two for Extra High, three for Max and four for Ultra or Ultracode. Lower levels have no strokes. Hover for the exact model and effort; screen readers get them too. You can also keep text codes under or beside the provider logo.

AI Usage puts your team’s Claude Code, Codex and Grok subscriptions on a page in BB: how much of each limit is left, when it runs out at the current pace, which machine used it, and what the subscriptions cost a month. What needs attention comes first, and a Team usage card sits in the sidebar footer. Invite people with a team key, or join theirs. It installs the open-source ai-usage collector if it’s missing; the collector runs every 15 minutes. It shows limits but never stops work at one.

It’s an unofficial fork of BB’s bundled Provider retry and takes its place. Hold a thread to keep it paused. Its optional extras, like the workflow resume, are off by default. It doesn’t resume BB’s own Workflows, and its recovery was tested on synthetic cases, not on real crashes.