Get it for macOS

See which parts of your system a thread's work touches, on a live diagram that redraws after every turn. Each part carries a tag: new, changed, impacted, or removed. Progress from the thread's plan bar fills the parts that each step builds, and flows play hop by hop to show what moves between parts. A second copy of the map opens as a browser page for another screen. A hidden mapper thread keeps the map current, so each update uses tokens on your provider; requires bb 0.48 or later.


Overview

View source

What you get

  • A Thread Changes Map tab in each thread's right panel. It shows a lane diagram of the system the thread works on: people, UIs, services, external systems, and shared host services.
  • Change tags on each part: NEW, CHANGED, IMPACTED (not edited, but the change affects it), and REMOVED. Parts with no tag did not change.
  • Plan progress from the thread's plan bar. Each phase has a bar, and the fill of each part shows the state of the plan steps that build it.
  • Flows that you play hop by hop with Back, Pause, Next, and Clear. Each hop shows what moves between the two parts.
  • Details for each part or edge when you click it: decisions, plan steps, calls, callers, and files.
  • A browser page with the same live map, for a second screen.
  • A bb thread-changes-map command to start, check, refresh, show, or stop a map.

How it works

Click Start thread changes map in the tab. The plugin starts a hidden mapper thread in the same workspace. The mapper reads the conversation, the plan bar, git status, and git diff, and draws a first map in a minute or two.

After each turn of the main thread, and at most every 90 seconds during a long turn, the mapper gets an update note and patches the map. The tab redraws in place. A ring pulses on the parts that changed, and a halo marks the parts the thread works on now.

The mapper writes the map through its own thread_changes_map_apply tool. Its instructions allow only read-only commands, such as git diff and cat. bb does not enforce this: the mapper shares the thread's workspace and permission mode. If the provider does not take a note, bb sends it again, up to 3 attempts in total.

Requirements and cost

  • bb 0.48 or later.
  • The mapper is a second agent thread. It uses the provider and model of the main thread, or the ones you set in the plugin settings. Each update costs tokens on that provider.
  • An idle mapper sleeps after 15 minutes. It wakes when the main thread finishes its next turn. Click Stop to end it.

More in Thread Content 99

Change what people see or do inside an open thread.

View all
Generative UITurns agent replies into charts, diagrams, maps, plans and forms you can use, right in the chat. Agents choose from 86 components on their own, with no setup: sliders and filters recompute in the page, and buttons, choices and forms put your answers in your message, which reaches the agent when you send it. Test reports, logs, lint errors and coverage files render as their own components instead of pasted text, and a thread's changes, commits, pull request and workers are read live from BB. Adds about 6,400 tokens of instructions to sessions whose replies you read, and looks up photos, places and map tiles on Wikimedia Commons, Wikipedia, Photon and OpenStreetMap unless you turn web lookups off. Relies on BB internals, so a BB update can show the blocks as code until the plugin catches up.ComicBit1.1K
Agent TracesSee where your agents' time goes, from every thread down to each command, tool call, and subagent of a turn. A turn opens as a timeline that splits the agent's time into waiting on you, tools, subagents, thinking, writing, and model time, and it grows live while the agent works. Select a call to see its exit code, output, and arguments, or jump to the reply that followed it in the chat. A Traces page in the sidebar compares your recent threads by active time, calls, and errors, and two turns can be compared phase by phase. Turns export as OpenTelemetry or an HTML snapshot, and the bb agent-traces command gives agents the same answers. Traces come from the thread history on your bb server; an OpenTelemetry collector is optional.Nicolas Charpentier390