Three plugins for bb, the agent IDE.
| Plugin | |
|---|---|
| Follow Up | Keeps the work an agent noticed but skipped, so nothing is lost when a turn ends. Triage what a thread accumulated above the composer. |
| Thread Badges | Shows pull-request state, CI attention, follow-up progress and listening ports on sidebar rows, so you see what needs you without opening a thread. |
| Workflow Stages | Files every thread under a workflow stage you define, and moves it as the work progresses. Requires the Ribbon sidebar. |
Each is independent. Three soft connections exist and none is required: Thread Badges draws a follow-up ring when Follow Up is installed and a ports plug when Worktree Ports is, and Workflow Stages needs Ribbon sidebar to have anywhere to draw.
One at a time, by subdirectory:
bb plugin install "git:https://github.com/matthewdias/bb-plugins.git@semver:*" \
--subdirectory plugins/follow-up --tag-prefix follow-up/
bb plugin install "git:https://github.com/matthewdias/bb-plugins.git@semver:*" \
--subdirectory plugins/thread-badges --tag-prefix thread-badges/
bb plugin install "git:https://github.com/matthewdias/bb-plugins.git@semver:*" \
--subdirectory plugins/workflow-stages --tag-prefix workflow-stages/Each plugin is released under its own tag prefix, so semver:* resolves to the
newest release of that plugin alone and these lines never go stale. A caret
range would: on a 0.x version ^0.1.0 cannot reach 0.2.0 at all, which is
how this page came to offer a plugin two minor versions behind.
--plugin <name> works instead of --subdirectory — the repository carries a
.bb/plugins.json index naming all three.
See each plugin's README for what it does, its settings, and its agent surface.
npm install
npm run check # typecheck, test, and build every pluginPer plugin:
npm run typecheck --workspace=bb-plugin-follow-up
npm test --workspace=bb-plugin-follow-up
cd plugins/follow-up && bb plugin install . && bb plugin devRequires Node 22 or later and a bb install providing the bb CLI.
MIT. See LICENSE.