smsunarto's bb-plugins

Plugins for bb, the agent IDE — in one GitHub repository.

Agent Providers

Amp

Runs Amp as a native bb provider, locally or in an Orb.

Dev Productivity

	Agentation	Turns a click on any part of bb into a structured annotation an agent can act on.
	GitHub Stack	Drives a gh stack from the thread panel — build, sync, submit, merge — and can hand the split to your agent.
	Traces	Explore Claude Code and Codex sessions, instructions, and tool activity with keyboard navigation and extensible event renderers.

Utilities

GTD Sidebar

An action-oriented thread list with Next Action and Waiting sections. Forked from bb's own example.

Themes

bb Monokai

A dark Monokai-family palette for the whole app: one meaning per hue, a single text ladder, all 16 ANSI colors, and a matching diff viewer.

Install

Add this repository as a marketplace once, then install by name:

bb marketplace add git:github.com/smsunarto/bb-plugins
bb plugin install gtd-sidebar

Adding a marketplace installs nothing — it caches the catalog, so these plugins become findable by name in bb plugin search and in bb's plugin browser. <id> is agentation, amp, gh-stack, gtd-sidebar, or monokai; if another marketplace you have added publishes the same name, spell it gtd-sidebar@smsunarto.

Every plugin ships as a git tag, and the catalog entry carries its release line. bb resolves the newest <id>/vX.Y.Z tag, clones it, installs the plugin's runtime dependencies, and builds both bundles against your bb — a plugin is never shipped prebuilt, so it always matches the host it runs on. bb plugin update <id> follows the same line.

Build from source

This is the route for unreleased work. It puts each plugin in as a local path source, so bb reads the files in place: edit, rebuild, reload — no reinstall.

git clone https://github.com/smsunarto/bb-plugins
cd bb-plugins
bun install                              # one hoisted node_modules at the repo root
bun run build                            # bb plugin build for every plugin
bb plugin install ./plugins/<id>         # from the repo root

Develop a plugin

Use BB's own build-and-reload loop for the plugin you are changing:

bb plugin install ./plugins/monokai
bb plugin dev ./plugins/monokai

The watcher targets the running BB selected by the CLI. It rebuilds and reloads the plugin on save. Use bb plugin source monokai, bb plugin list, and bb plugin logs monokai to inspect it. Run focused tests with BB's SDK testing harnesses, then verify the changed user flow in the app.

Test another BB build

Use BB's own launcher from the BB checkout, following its docs/debugging-and-qa.md:

cd ~/git/bb
scripts/bb-dev-app current
scripts/bb-dev-app status
eval "$(scripts/bb-dev-app env)"
pnpm bb:dev plugin install /absolute/path/to/bb-plugins/plugins/monokai
pnpm bb:dev plugin dev /absolute/path/to/bb-plugins/plugins/monokai

The launcher reports the build's URLs, data directory, and logs. Use scripts/bb-dev-app stop when finished. This repository does not manage BB checkouts, ports, or server processes.

Documentation screenshots

bun run screenshots renders static documentation heroes without a BB server. bun run screenshots:fixtures requires BB_APP_URL, set to the launcher's reported App URL, which differs from its API server URL in development. Prepare the affected plugin, GTD sidebar, and bb Monokai through BB before capturing live fixtures. Capture checks their source, running state, and selected palette without changing them.