Get it for macOS

Run your project's dev server, tests and scripts from a menu in each thread's header, in that thread's own worktree. The list is a .bb/actions.json file in the repository, so each branch carries its own actions and everyone on the project gets the same menu. Picking an action opens a terminal titled with its name in the thread's terminal panel, and picking it again while it runs brings that terminal back instead of starting a second copy. Edit actions… opens an editor beside the thread that adds, changes, reorders and deletes actions, checks each change and saves into the worktree without committing. Requires bb 0.49 or later; actions run on macOS and Linux machines.


Overview

View source

The actions file

The list lives in the project, in .bb/actions.json, committed like any other file. Each action has a name and a command, and optionally a folder to run in (relative to the repository's root) and a description for the menu. Because the file is read from the thread's own workspace, every worktree sees its own branch's version, and a thread on another bb machine reads that machine's copy. Edits show up the next time the menu opens.

Editing actions

Edit actions… in the menu opens an editor beside the thread: add, change, reorder and delete actions in a form, or edit the file as JSON. It checks each change the way the menu does and will not save a file with a mistake. Saving writes the thread's own copy of the file, creating it when there is none, without committing it, and it will not overwrite a file that changed on disk since you opened it.

Running an action

Picking an action starts a terminal titled with its name. The command runs in your login shell, so your PATH and your shell's syntax work as in a terminal you opened yourself.

  • An action that is still running is marked Running; picking it again shows its terminal instead of starting a second copy.
  • A finished action keeps its output and a line with its exit code until you run it again, which starts a fresh run in its place.
  • Ctrl+C stops a command; closing the terminal's tab ends it.

Runs are per thread, so two threads in two worktrees can each run their own dev server.

When something is wrong

A project without the file gets a short explanation of how to add one. A file with a mistake, such as a misspelt field or a missing comma, shows the problem with its line, column and the action it is in, rather than a broken menu.

Requirements

bb 0.49 or newer. Actions run on macOS and Linux machines. Nothing to configure, and nothing is sent anywhere: the plugin runs only the commands in the project's file, in folders inside the workspace, and writes only that file. Starting an action and saving the file are the plugin's RPCs, which the menu and the editor call and which other clients you trust with your bb (plugins, scripts) can call too, as with any bb plugin.

More from Gustavo Ambrozio

ChatGPT Realtime ConnectionRun Voice Mode's voice chats on your ChatGPT subscription instead of a separately billed OpenAI API key. It hands Voice Mode the ChatGPT sign-in that the Codex CLI already keeps on the machine running the bb server, reads it again for every chat, and never renews or rewrites it. Only the plugins you allow, Voice Mode to begin with, receive the token; the bb app, the command line and agents in threads never do. This is an undocumented use of the subscription that OpenAI could stop accepting at any time, nobody has checked whether OpenAI's terms allow it, and voice chats count against your ChatGPT plan. Requires bb 0.46 or later, Voice Mode 0.1.9 or later, and the Codex CLI signed in with Sign in with ChatGPT on a plan that includes Codex.26Diff ReviewComment on a thread's changes line by line, then send the comments to its agent, which fixes the code and answers each one. A Review tab beside the thread shows the diff of its uncommitted, staged or unstaged changes, its branch, one commit or a range, and each comment follows its code as the code moves. The same tab reviews a GitHub pull request: answer its threads, mark files viewed in step with GitHub, and submit your comments as one review, posted as the GitHub CLI's signed-in account. An AI review leaves comments of its own, @reviewer answers a question inside a comment thread, and Fix in a new thread hands the comments to another agent; these runs start as threads under the one being reviewed, in the permission mode set in the settings (bb's Approve for me by default, or Accept edits), and in full permission mode with a provider that lacks that mode, such as opencode. Follows the review loop of the open-source diffity, credited in the plugin's third-party notices. Needs bb 0.48 or later with bb's Git plugin on, and the signed-in GitHub CLI (gh) for pull request review only; it is built on experimental bb plugin APIs that may change between bb releases.NewDreamKeep every Claude Code project's memory consolidated overnight, as Claude Code's own auto-dream would if it ran in bb. Each dream is a hidden thread that can read anything but write only that project's memory files, and a project's first dream is a dry run you review as a diff, then apply or discard. The memory is backed up before every change, and the Dream page shows each project's memory, why it is or is not due, the dry runs waiting for you and the history of dreams. The schedule is off until you turn it on. Each dream is one model run on your Claude Code account; requires bb 0.49 or later, macOS or Linux, and Claude Code signed in on the machine dreams run on.NewFirstMate CrewHand one agent your to-do list and it runs a crew of worker threads, each in its own git worktree, until the work lands. The first mate is a pinned thread in bb's own chat that writes each worker's instructions, supervises it, and brings back branches, pull requests, findings and only the decisions that are yours. A FirstMate tab shows the crew as a board of Queued, Working, Blocked, Parked, Done, Failed and Idle, with Steer, Interrupt, Relaunch and End on every card. A built-in watch tells the first mate within about five minutes when a pull request is merged, reviewed or changes check status. Requires bb 0.47 or later, git, and the logged-in gh CLI for the pull request watch; a capable model such as Claude Sonnet is recommended for the first mate.14

More in Command Line 12

Work with shells and command-line programs inside bb.

View all