Impromptu UI

Generate interfaces for what you need to process or act on, instead of walls of text in chat. An agent's results, such as issues to triage or a Dependabot pull request to merge, appear as rows above the composer, one per item. Each row opens a side panel with the details, a draft you can edit, and buttons that post it, start a thread, run a command once you confirm it, or open a link. For design choices, a film strip shows screenshots of the original and each alternative, and Send feedback returns your pick and notes to the thread. The agent reads back what you did and carries on from there. Requires bb 0.43 or later, and needs no account or external service.

Overview

View source

What you get

Rows above the composer, one per item an agent wants you to act on, such as issues to triage or a Dependabot pull request to merge.
A side panel for each item, with its details, a draft you can edit, and buttons that post the draft, start a thread, run a command once you confirm it, or open a link.
A film strip for picking a design: screenshots of the original and its alternatives, a note on each, and Send feedback, which sends your pick and notes to the thread.

How it works

A skill writes its results as a view file and publishes it from the thread. Done and dismissed items sink to the bottom, and the agent reads back what you did. Views are stored in the plugin's own database on this machine.

For agents

Agents get the impromptu-ui skill and the bb impromptu-ui command: publish, state, hide, and list. The refine-impromptu-ui skill files an anonymized issue when a view falls short.

Requirements

Nothing to configure. A command button runs with your permissions, so read the command before you confirm it.

More from Daniel Bachhuber

Automation PaletteRun any bb automation from the quick palette, without opening the Automations page. Each row names the automation and its project, so typing either name finds it, and selecting it starts the run as its schedule would. Every project's automations are listed in every window, and a paused automation keeps its row. Requires bb 0.42 or later and the bb CLI on the machine running the bb server.2 Diff ViewedUse a Viewed checkbox on each file to keep track of what you've read in a long diff, synced with GitHub on the thread's pull request. Checking a file collapses and dims it, and the toolbar counts how far you have got, such as 3/6 viewed. A mark clears itself when the file's diff changes, so a rebase or a new hunk puts the file back in front of you. An Only unviewed filter hides the files you have read. Requires bb 0.41 or later, and GitHub sync needs the gh CLI signed in.19 Markdown EditorEdit a markdown file in the tab you were already reading it in, and save it with Cmd+S. Preview renders the file the way bb renders a chat message, including the images it points at, and Raw gives you the source in an editable pane, with unsaved text carrying between the two. Selecting text in Preview offers an Add to chat button that quotes it into the composer under the file's path. A pencil on markdown files in the changes panel opens the one you are reading a diff of. Every save checks the file's hash first, so an edit an agent made while you were typing gives you a choice between reloading and overwriting instead of a silent clobber. Works on files in a project workspace, on a host, or in a thread's storage. Requires bb 0.43 or later, and needs no account or external service.10 TokenomicsUnderstand what your threads cost in tokens and time, so you can cut what isn't worth it. Each thread's header shows a sparkline of its token use that opens a summary of which of your messages used the most tokens and time. Once a thread's context passes a size you set, a meter above the composer offers to compact it, and the sidebar counts those threads. A Tokenomics page charts tokens by hour or day, shows where turn time went, and ranks threads by use. Requires bb 0.43 or later, and counts Claude Code subagents only for threads that ran on the same machine as bb.New