Get it for macOS

See every skill a thread's agent can use, where each one comes from and what it says, and add one to the chat from the panel or composer. A Skills tab in the thread's side panel groups them by origin — the project, the repository, your personal folder, an admin folder, a Claude Code or Codex plugin, or bb itself — and shows each one's SKILL.md, rendered, with its path on disk. Claude Code, Codex and Hermes threads have their skill folders read the way that agent reads them, in worktrees and on other enrolled machines too, so a name defined twice is listed once, under the copy the agent uses. Add to chat puts the skill in the message box as the same pill bb's / menu inserts and sends nothing, and a Skills button with a live count, or a keyboard command, opens the same list in bb's pop-up above the message box. Threads on other providers list bb's own skills and what bb's / menu offers. Needs bb 0.45 or later, and no account, key or network access.


Overview

View source

A skill's name in the / menu says little: which copy will the agent load, where does it live, and what does it tell the agent to do? Skills answers that for one thread at a time, next to the conversation.

What you get

  • A Skills tab in each thread's side panel, listing every skill that thread's agent can use, grouped by origin: the project, the repository, your personal folder, an admin folder, a Claude Code or Codex plugin, or bb itself.
  • Each skill's SKILL.md, rendered, with its path on disk and a button to copy it.
  • Add to chat: puts the skill at the start of the thread's message box as the same pill bb's own / menu inserts, with the cursor after it for any arguments. Nothing is sent until you send it.
  • A Skills button in the composer with a live count, opening the same list in bb's own pop-up above the message box (a sheet on a narrow window), and a command palette entry for the tab.
  • A command to open that list from the keyboard, in whichever message box has the cursor. Give it a key in bb's keyboard settings.

How it finds them

  • Claude Code, Codex and Hermes threads have their skill folders read the way each agent reads them: from the thread's directory up to the repository root, then your home folders, plugins last. A name defined twice is listed once, under the copy the agent uses.
  • Claude Code plugins installed for a repository are listed in its worktrees too, as Claude Code applies them there.
  • Hermes's archived and organisation-mirror folders are left out, as Hermes leaves them out.
  • Every thread also lists the skills bb adds to all threads, and what bb's / menu offers that has no file, such as an agent's built-in commands.
  • The files are read on the machine the thread runs on, including another enrolled machine.

What it needs

  • bb 0.45 or later. No account, key or network access.

Limits

  • Built-in skills that live inside an agent's program have a description but no file to show.
  • Skills on other providers come only from bb's own list and bb's / menu.
  • Codex skills switched off in Codex's settings, and Claude Code plugins switched off for a project, are still listed.
  • Hermes profiles, and Hermes or Codex homes moved by a setting the agent alone sees, are not followed.

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 Memory & Context 21

Control durable knowledge or standing context available to agents.

View all