Get it for macOS

Show fewer sidebar icons on your phone than on your desktop. Phone-sized screens keep their own set and order of rail icons, while desktop windows keep bb's shared choice. Customize navigation on a phone, or Customize phone navigation in the desktop rail's More menu, opens bb's own list to tick and drag icons, and Same as wider windows goes back to the shared set. The phone's set is saved on your bb server, so it survives restarts and every phone shares it; a desktop window narrower than 768 pixels counts as a phone too. Requires bb 0.48 or later; pick Phone Rail in Settings → Appearance → Navigation.


Overview

View source

bb keeps one list of sidebar icons for every device, so hiding an icon on your phone hides it on your desktop too. Phone Rail is bb's own icon rail with one difference: phone-sized screens keep their own set of icons, in their own order. Wider windows keep bb's shared choice.

What you get

  • On a desktop window, bb's rail as you know it: the same icons, order, badges and menus, and bb's own Customize navigation editor.
  • On a phone, the phone's own icons. Until you change anything, that is the same set as everywhere else.
  • Customize navigation on a phone opens bb's customize list in a sheet: tick an icon to show it, drag to reorder it. Hide from rail on a phone hides the icon there only.
  • Same as wider windows drops the phone's set and goes back to the shared one.
  • Customize phone navigation in the desktop rail's More menu sets up the phone from the desktop.
  • Hidden icons stay reachable in More. A plugin page installed after you set up the phone starts in More there.

Set it up

Pick Phone Rail in Settings → Appearance → Navigation. With Navigation on Automatic, installing it picks it already. Set Navigation back to Rail, or disable the plugin, to return to bb's own.

What counts as a phone

bb tells a navigation plugin whether it is using its compact (phone) layout: a window narrower than 768 pixels. That covers the iPhone app and a phone's browser, and also a desktop window made that narrow. bb does not say which device is asking, so every phone shares one set, saved on your bb server.

Requirements

bb 0.48 or later. No account, service or API key.

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 Themes & Appearance 72

Personalize how bb looks and feels.

View all