Awesome bb plugins

Community plugins for bb — the agent IDE that builds itself.

bb ships 13 official plugins bundled inside the app and deliberately has no remote marketplace, so third-party plugins are found by word of mouth. This list is the missing directory.

Two install forms. Everything here installs from git:

bb plugin install git:https://github.com/<owner>/<repo>.git@main

Some now publish to npm as well — 16 packages carry the bb-plugin keyword as of 2026-08-12 — and where an entry lists one, that is the shorter route:

bb plugin install npm:<package>

A plugin living in a subdirectory of a monorepo cannot be installed with the git: form at all — bb reads the manifest at the repo root (get-bb/bb#1097). Use the npm package where the entry names one, otherwise clone the repo and bb plugin install <path>.

(@bb/plugin-sdk itself is still unpublished; plugins vendor it. That blocks the SDK, not the plugins.)

Plugins are full-trust code running in the bb server. Read the source before installing.

Contents

• Providers · Threads & workflow · Editing & files
• Code intelligence · Host & environment
• Memory & knowledge · Notifications
• Integrations · Appearance · Fun
• Authoring tools · Writing a plugin · Contributing

Providers

• bb-plugin-kimi — Kimi Code as an ACP provider.
• bb-plugin-factory-droid — Factory Droid as an ACP provider.
• omp — OMP provider integration.
• amp — Amp as an ACP provider through a bundled bridge over the official @ampcode/sdk; /orb in a thread's first prompt runs it in an Amp Orb sandbox, and Oracle sub-agent calls render as a card with a streaming trace. · npm @smsunarto/bb-plugin-amp

Threads & workflow

• bb-plugin-advisor — reviews a coding thread with a second model in a hidden reviewer thread; a pre-final agent tool plus post-turn review, with findings that re-raise across turns until the reviewer re-checks and closes them.
• bb-plugin-bus — peer messaging between threads; addressed sends wake the recipient with a real turn, so no listener process is needed.
• bb-plugin-auto-sections — files task-keyed threads into sidebar sections automatically.
• thread-organizer — organize threads in the sidebar.
• thread-hover-cards — preview a thread on hover.
• timeline-comments — comment on the thread timeline.
• bb-plugin-next-steps — suggests next steps above an empty composer.
• prompt-shaper — improve a prompt before sending it.
• auto-new-tab · sessions · prime-agent
• bb-plugin-todo — hierarchical session todos with nested sub-tasks, dependsOn/requires, and dispatch to multiple agents.
• bb-plugin-session-goal — keeps a session's goal and success criteria on a composer card so they stay in view.
• agentation — click any element of the bb UI, including another plugin's surface, and file it as an annotation carrying the route, owning plugin id and DOM selector; staged batches are assigned to a thread from its composer, and agent tools acknowledge, reply to and resolve them. · npm @smsunarto/bb-plugin-agentation
• t3sidebar — replaces the sidebar thread list with a flat inbox that never re-orders; snooze a thread to a wake time or settle it, which also archives it in bb, and live work blocks parking. Forked from bb's own examples/plugins/t3sidebar and built on experimental SDK slots. · npm @smsunarto/bb-plugin-t3sidebar
• Thread tasks — replaces the sidebar thread list with manually ordered Done/To do/Working/Waiting/Deferred/Canceled sections, moves a thread to Working when its turn starts and back to To do when it stops or blocks on the user, and adds . status chords plus a bb task list|show|update CLI.
• Missing keyboard shortcuts — adds the shortcuts bb does not bind: ⌘[/⌘] for browser history, ⌘N/⇧⌘N for a new thread with or without the current thread's project, ⌘L to focus the primary composer, and ⇧⌘L / ⌃` to toggle a side chat or thread terminal.
• emoji-react — adds one emoji button per configured reaction to the assistant-message text-selection menu; clicking one drafts a reply quoting the highlighted text.
• bb-plugin-writing-check — checks each English message you send for spelling and grammar in a hidden worker thread and inserts the corrections below the message; explanations are written in Simplified Chinese.
• Agent Checklists — gives a thread a persisted list of steps the agent reads and ticks off through agent_checklist_get / agent_checklist_update, with progress in the workbench and a read-only detail view; state lives in the plugin's own SQLite store.
• Comprehension — turns a message, a text selection or a whole thread into an HTML explainer, from a message action or the thread header. Needs bb ≥ 0.38.
• Plannotator — embeds the upstream Plannotator plan-review app in the thread panel and hands its approval or feedback back to the agent via a plannotator_review_plan tool; you supply the Plannotator binary yourself.
• Cascade — niri-style scrollable tiling: every live thread is a column in a horizontally scrolling strip, rows group those columns by section, project or machine, and hjkl moves while HL reorders.
• T3 Sidebar — inbox-style replacement for the sidebar thread list, and the reference example for app.slots.experimental_threadList published standalone from bb's own examples; bb's list comes back the moment you switch away. · npm bb-plugin-t3sidebar
• Dispatch — expands a one-liner into a full prompt and routes it to the right project as a new thread, from the new-thread composer.
• Arc Switcher — ⌘D cycles the seven most recently opened threads, Arc-style; each one keeps a stable emoji marker so it stays recognisable as the most-recent order shuffles under it. Ships no LICENSE, so strictly nobody has been granted the right to use it yet.

Editing & files

• bb-plugin-files — file browser and editor for a thread's environment.
• bb-plugin-filetree — lazy-loading file tree in the side panel.
• Git Graph — read-only commit graph in a thread side panel, running git inside that thread's own environment — including one hosted on another connected machine, rather than on whichever repo the bb window happens to be pointing at.
• bb-plugin-md-annotate — Google-Docs-style inline comments on markdown.
• excalidraw — Excalidraw boards inside bb.
• bb-plugin-excalidraw — opens a workspace .excalidraw file as a canvas, with SHA-256 compare-and-swap agent tools, a bb excalidraw read/create/apply CLI, and a diagram-design skill.
• Server File Explorer — read-only Files panel for the machine running the bb server, with folder navigation, an absolute-path bar, browser history and markdown shown rendered or raw.

Code intelligence

• bb-plugin-code-intelligence — tree-sitter code search and impact analysis. (unmaintained — upstream archived the repo)
• design-doctrine — design guidance for agents.

Host & environment

• bb-plugin-system — CPU, memory, disk and top processes as a panel, homepage tiles and a bb system CLI.
• Wterm Terminal Preview — early-preview Ghostty-backed alternative to bb's thread terminal with persistent reattachment, TUI mouse input, font controls and file upload for SSH and Herdr workflows. Drives bb's own terminal sessions rather than spawning its own, and uploads land in .bb-wterm-uploads/ under the terminal's working directory. Built on an experimental SDK slot, so it is more exposed to bb UI churn than most entries.
• bb-plugin-worktree-setup — per-repo worktree provisioning and git hooks.
• browser — shared Chrome over CDP.
• bb-plugin-browser — drives a browser you already have (Brave, Chrome, Chromium, Edge, Vivaldi or Opera) over CDP on a profile of its own, headless by default; each thread gets its own tab named by CDP target id, so tabs survive plugin reloads and bb restarts, threads share cookies and logins but can never move each other's page, browser_show relaunches on screen when a login wall or CAPTCHA needs you, and the idle reaper only ever closes tabs the plugin opened.
• stay-awake — keep the host awake while work runs.
• codex-environments — Codex environment management.
• bb-plugin-accounts — Claude Max account usage and auto-switching, with thread auto-continue after a rate limit.
• bb-plugin-cf-tunnel — reach bb remotely over your own Cloudflare Tunnel and Access policy, with expiring shared ports.
• agent-proxy — installs CLIProxyAPI and keeps it running as a launchd/systemd login service, so several Claude and Codex accounts answer on one loopback OpenAI/Anthropic/Gemini endpoint; OAuth sign-in, provider keys, usage and Claude Code/Codex wiring in a panel, plus a bb agent-proxy CLI. It installs a third-party binary as a login service that outlives bb. · npm @smsunarto/bb-plugin-agent-proxy
• usage-tracker — Codex and Claude Code usage percentages in a sidebar footer strip that expands to the 5-hour and weekly windows with reset times. · npm bb-plugin-usage-tracker
• bb-plugin-usage — token counts and estimated API cost per agent, model provider and machine, read from Codex, Claude Code, Grok, OpenCode and Pi session logs on every enrolled host.
• Usage — a second take on the same idea: Claude Code, Codex and Pi token usage and estimated cost in a nav panel and a CLI, read from local session logs on the host running bb.
• Usage limits below chat — one compact row under the composer showing the session and weekly limits of the provider selected in that composer — Codex, Claude Code or Cursor — with the signed-in account on the right.
• Grok Usage — adds a Grok Build weekly-limit row to Settings → Usage limits, reusing the existing grok login session in ~/.grok/auth.json instead of asking for another key.
• Lanes — normalises Claude, Codex, OpenCode Zen Go and OpenRouter headroom into one set of gauges on the homepage and a nav panel; the last two are the lanes bb tracks nothing about.
• Toolbox — one registry for MCP servers and named CLI operations, re-exposed to any provider as bb agent tools and as a single aggregated MCP endpoint. Enabled entries run real commands, so read what you turn on.

Memory & knowledge

• bb-plugin-memory-ui — browse, search, edit, pin and forget bb memories, with version history.

Notifications

• bb-plugin-ios-notifications — Web Push to your iPhone when a thread finishes or fails.
• bb-plugin-notify — agent-to-user pings as an in-app toast or a webhook, with quiet hours.
• notify — native macOS notifications when a thread finishes or fails, posted by the bb window so they carry bb's icon and click through to the thread; holds them in a durable queue while bb is closed, plus a notify_user tool and a bb notify command. · npm @smsunarto/bb-plugin-notify

Integrations

• linear — search Linear issues from the prompt box and attach agent-ready context.
• bb-plugin-linear — the deeper of the two Linear entries: issues, inbox, triage, projects and cycles in a nav panel, each thread bound to the issue it works on in the header and in the agent's own context, and a dozen linear_* tools covering search, comment and issue create/update.
• Shortcut — the Shortcut stories assigned to you as a compact kanban grouped by workflow state, with shortcut_list_assigned / shortcut_get_story agent tools and a hand-off into a thread; the API token is a secret setting.
• Beads — browse and update Beads issues in a project panel, shelling out to the bd CLI as the source of truth rather than keeping its own copy; Beads must already be installed.
• bb-plugin-jenkins — a second Jenkins plugin, aimed at deploys rather than browsing: star the jobs you ship, group them into your own folders, and fire parameterised builds or saved presets in one click, with live status on the homepage.
• telemetry — usage telemetry.
• bb-plugin-exec-tracking — records provider/model/reasoning evidence per run.
• bb-plugin-argocd — read-only Argo CD browser: application sync and health, managed resources, deploy history and pod logs, with agent tools and a bb argocd CLI.
• bb-plugin-jenkins — Jenkins jobs, builds and console logs as a panel, with agent tools, a bb jenkins CLI, and build triggering behind a confirmation.
• bb-slop-cop — polls GitHub for PRs matching rules you define, dispatches a bb agent to review each match, and posts the review with gh; new rules run in shadow mode and only review authors with write access.
• gh-stack — drives gh stack in a thread's workspace: a layer rail with each PR's state and +N −M diff, checkout with auto-stash, draft toggle, sync/submit/merge/prune, and a button that hands the split to the thread's agent. · npm @smsunarto/bb-plugin-gh-stack
• taskboard — per-project GitHub, Linear or Jira issues as a list or kanban board, with drag-to-move through the provider's own statuses, a bb taskboard CLI, and a mention that attaches a task's context to a prompt. · npm bb-plugin-taskboard

Appearance

• bb-plugin-ayu — ayu themes plus a palette explorer.
• bb-plugin-sidebar-sync — keeps the sidebar arrangement — nav order, hidden rows, collapsed sections — the same in every bb UI; width and open state stay per-device.
• ds4 — design-system theming.
• bb-plugin-fontsize — scales the whole interface from a sidebar footer button that cycles 13/16/20/26px, plus a settings panel with ±1px control; the size is stored per device.
• monokai — dark Monokai palette that also repaints the terminal's 16 ANSI colors, the diff viewer's rows and gutters, the file tree's git-status column, inline code tokens and the composer stop button; dark appearance only. · npm @smsunarto/bb-plugin-monokai
• Project header breadcrumb — puts the project name before the thread title, with a menu for project settings, rename and remove.
• Project icons — gives each project an icon and optional color, picked from a 2,532-icon Hugeicons catalog and drawn before the project name in the thread header.
• Cobalt2 — the Cobalt2 palette as a bb theme; CSS only, no server behaviour.
• HUD — a Claude-Code-style status line on the composer: which model is answering, its reasoning level, how much of the context window the thread has eaten, and the token counts.
• Agent Orbs — gives each active child thread a stable identity: a generated Oreo avatar and a friendly codename.
• Composer Beam — draws an animated beam around a composer while its thread is running or submitting. Frontend only.
• Fluid Thinking — replaces only the Thinking… / Working… indicator with the morphing Fluid Functionalism one.

Fun

• bb-plugin-strudel — Strudel live-coding music REPL, with agents.
• bb-plugin-ambient-live — sample-browser ambient DAW.

Authoring tools

• Plugin Studio — inspect the plugins your bb has actually loaded from a nav panel: a read-only snapshot of their source and status, taken in-process rather than by starting a second runtime.
• bb-smithers-workflows — plugin verification and release-gate workflows.
• create-plugin / validate-plugin-artifacts — scaffolding and artifact validation scripts.

Writing a plugin

bb plugin new <name> scaffolds one. The authoritative reference is the bb-plugin-authoring skill shipped inside the app; bb plugin types writes the SDK type declarations into your types/ directory.

Conventions this ecosystem has settled on:

• Name the repo and package bb-plugin-<thing>.
• Tag the repo with the bb-plugin topic — that is currently the only way anyone finds you.
• Pin engines.bbPluginSdk (^0.4.1 at time of writing); managed installs refuse a mismatch.
• Put every runtime import in dependencies, not devDependencies — zod above all. Managed installs run npm install --omit=dev, so a devDependencies entry that server.ts imports fails the build and the plugin cannot be installed at all. This is the single most common breakage on this list.
• private: true is fine and does not block a git: install — it only stops npm publish. (This entry used to claim the opposite. Verified against the installer's own steps on 2026-08-15.) It does mean there is no npm package, which matters if you are in a monorepo.
• Ship a LICENSE. Without one, the default is all rights reserved, and a directory that tells people to install your plugin is asking them to do something you have not permitted.
• Ship a prebuilt dist/ if you publish to npm: npm installs run --ignore-scripts and never build. Point bb.server at your source (./server.ts), not at ./dist/server.js — a manifest that targets a committed artifact means the code that runs is not the code a reader reviews.

Contributing

Pull requests welcome. One entry per plugin: link, then a single sentence describing what it does, in the section that fits. Keep it factual — no marketing copy. A plugin qualifies if its package.json has a bb key or it imports @bb/plugin-sdk.

License

CC0-1.0 — public domain.