Ribbon Suite

Grow your swarm. Don't lose the thread.

A suite of bb plugins for managing large amounts of agents.

Plugins

 Ribbon sidebar

Organize threads by projects, sections, and provider-defined groupings in one sidebar.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install ribbon-sidebar@ribbon

Read more →

 Thread stages

Provide workflow stages, automation, and shortcuts to Ribbon sidebar.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install ribbon-sidebar@ribbon
bb plugin install thread-stages@ribbon

Read docs →

 Icons

Give each section and project an icon and color.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install icons@ribbon

Read docs →

 Breadcrumbs

Show a thread's section, project, and ancestors in its header.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install breadcrumbs@ribbon

Read docs →

 Missing keyboard shortcuts

Add shortcuts to start personal or project threads, navigate history, and reach the composer or panel tabs.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install missing-keyboard-shortcuts@ribbon

Read docs →

 ChatGPT theme

Restyle bb to match the OpenAI ChatGPT (Codex) desktop app.

bb marketplace add git:github.com/ariofrio/ribbon
bb plugin install chatgpt-theme@ribbon

Read docs →

Updating

bb plugin update <entry-id> moves an installed plugin to its newest release. Once the marketplace is added, its other plugins can also be picked in Settings → Plugins.

Development

Clone the repository and install every plugin at once:

git clone https://github.com/ariofrio/ribbon.git
cd ribbon
npm run install:plugins

Run the same command after a git pull: it installs whatever is missing, then rebuilds and reloads every plugin.

To run one plugin's unreleased code without a checkout, install it from main by its entry name in the collection — the entries are listed in .bb/plugins.json:

bb plugin install git:https://github.com/ariofrio/ribbon.git@main --plugin chatgpt-theme

That install follows the branch rather than the release tags, so bb plugin update <plugin-id> moves it to the newest commit on main.

Releases

Create a Changeset with npm run changeset for every user-visible plugin change. After the change reaches main, automation opens or updates a release pull request with version, lockfile, and changelog updates. Merging that pull request validates the affected plugins, creates immutable <plugin-id>/vX.Y.Z Git tags, and publishes a GitHub release per tag carrying that version's changelog entry. Every listing accepts any released version, so the catalog never changes with a release. Nothing is published to npm yet.

npm run release:check runs each plugin's tests, type checks, build, SDK declaration verification, and packed artifact verification. CI runs the same check for every plugin. Build output in dist/ is generated and is not committed.

License

MIT