smsunarto's bb-plugins

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

Agent Providers

	Agent Proxy	Pools several Claude Code and Codex subscriptions behind one local endpoint and load-balances across them, moving on when one hits its quota.
	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.

Utilities

	Notify	Real macOS notifications from bb itself when a thread finishes or fails, plus a notify_user agent tool.
	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 notify

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 agent-proxy, agentation, amp, gh-stack, gtd-sidebar, notify, or monokai; if another marketplace you have added publishes the same name, spell it notify@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 bb plugins against an isolated bb

Goal	Command	bb source
Develop plugins against the current release	bun run dev	Managed release checkout
Develop plugins against another revision	bun run dev:instance -- --revision <selector>	Managed branch, tag, or commit checkout
Develop bb with uncommitted source changes	bb-kit dev-instance start --attach .	Existing checkout in place
Run tools against the selected instance	bb-kit dev-instance run -- <program>	Current managed or attached source

Start the latest bb release, build the workspace, apply the baseline, and run the plugin watchers:

bun run dev

The command routes the build, baseline, and watchers through one managed bb instance. It does not reload agent-proxy automatically.

To prepare the fixture without starting watchers, run:

bun run dev:instance

The prepare-only command installs workspace plugins, pins experiments, resets plugin settings, and selects the repository theme. It is safe to repeat. Pass any owned bb-kit start selector after -- when you need another revision or a named instance:

bun run dev:instance -- --name my-branch \
  --revision local:my-branch \
  --repo ~/git/bb

Use bb-kit dev-instance directly when you need lifecycle control without the bb-plugins baseline. bun run dev:instance refuses --attach because the baseline resets instance plugin state.

Develop bb core from its checkout

Attach bb-kit to the checkout that you are editing:

cd ~/git/bb
bb-kit dev-instance start --attach .
bb-kit dev-instance run -- pnpm test

The attached instance uses that checkout in place. bb-kit preserves dirty files and never removes the checkout, its data directory, or its logs.