[kalindudc]

Plugin

Burn shows what every agent thread costs in dollars while it runs, per prompt and across all threads, whatever harness runs the thread (pi, Codex, Claude Code or another).

• A chip beside the context circle under the prompt box shows the thread's total and what the last prompt added. Its card breaks the cost into input, cache write, cache read and output, charts every model call, lists the models, and adds the cost of child threads such as minions. From the card you can set a budget, open the Burn tab or copy a summary.
• A Burn tab in the thread's side panel lists every prompt's cost, newest or costliest first, and the thread's children with their cost.
• A Burn page in bb's navigation shows spend across all threads for today, 7 or 30 days, by day, project, model and harness, ranked by cost, tokens or calls.
• Every thread menu gets a Cost entry, and threads over their budget get a red flame in the sidebar.
• Budgets notify at 80% and 100% of a thread's budget. Burn never stops a thread unless the "Stop a thread at its budget" setting is on, and it is off by default.

Where a harness records no cost (Codex and Claude Code pass bb tokens only), Burn prices the tokens with pi's list prices and marks the amount as an estimate, for example ~$1.23.

Source

https://github.com/kalindudc/burn, repository root, range >=0.4.0 <1.0.0 (latest tag v0.4.0). The same repository also ships an optional pi extension, which pi installs separately and bb does not need.

Checks

Plugin:

• npm test: 398 tests in 32 files pass
• npm run typecheck passes
• bb plugin build builds the server, app and host bundles
• the same code ran on my own bb 0.46.1 install as 0.3.1, under the earlier ID pi-burn; 0.4.0 only renames the package to burn

Marketplace:

• npm run build: built with 415 entries, no errors
• npm test: 46 of 46 pass
• npm run gate:v1: passes; 1 new entry needs no exception
• npm run check: passes, including the source check that finds the v0.4.0 tag (the "unchanged entry files have no category" warning is pre-existing)

Permissions and services

• No outbound network calls and no outside service. The list prices are bundled in the plugin.
• A host entry runs on each connected bb machine. It only reads the pi session logs in bb's pi bridge folder (~/.bb/pi-bridge-sessions), watching the folder and reading only appended bytes.
• The server adds one plugin HTTP route, POST /usage, and passes its address to pi sessions in the BURN_BB_URL environment variable, so the optional pi extension can report budgets and stops.
• It reads threads and their usage events through bb's thread APIs, and stops a thread through bb only when the off-by-default stop setting is on.
• Its plugin storage holds usage reports, a copy of the usage events it read (bb deletes older ones), thread budgets and stop times. It deletes a thread's data when the thread is deleted.
• The sidebar flag and the host entry use experimental bb APIs; on a bb without them the flag does not show.

Screenshots

Real plugin surfaces with made-up projects and threads, captured in a sandboxed bb:

• chip-card.png: the cost chip under the prompt box with its card open
• side-panel.png: the Burn tab, with every prompt's cost and the thread with its child
• burn-page.png: the Burn page for the last 30 days: cost and usage cards, spend per day by model, token mix and call time
• burn-page-tables.png: the Burn page's costliest threads, models table, and spend by project and by harness

Overview

Copied from the plugin repository's PLUGIN_OVERVIEW.md. The icon file name burn-9fbcc076.svg carries the first 8 characters of the icon's SHA-256 hash, and it is the same single-colour icon the plugin manifest uses.

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

Reviewed and verified the submitted change under the maintainer admission policy. Required CI passes; approved for merge.