Get it for macOS

Run your go-to skills in one tap from chips beside the send button, instead of typing them through the / menu each time. Each chip either drops its skill, with preset arguments, into your draft or sends it right away. Select text in the chat or in your draft first, and the chip passes it to the skill as the argument. Add as many chips as you need in the plugin settings; they scroll sideways, fold into one toggle, and shrink to emoji on phones. Needs no account or external service.


Overview

View source

What you get

  • One tap instead of typing. Pick the skills you use most, such as code review, debugging or planning, and each gets a chip with its emoji and label next to the send button. Chips appear in every thread and on the New thread page.
  • Insert or send. An Insert chip puts the skill, plus any arguments you preset, at the start of your draft so you can add details before sending. A Send chip submits it immediately, together with whatever you already typed.
  • Selected text becomes the argument. Select a passage in the chat, then tap a chip: the skill arrives with that text as its parameter. Select words inside your draft and the skill is placed right before them.
  • Room for as many chips as you want. When they do not fit, the strip scrolls with the mouse wheel, trackpad or a swipe. The » toggle folds all chips into one, and the choice is remembered across reloads and devices. On narrow screens such as phones, chips shrink to their emoji.

Set it up

Open Settings → Plugins → Skill Dial. For each chip choose a skill (suggestions come from the same list as bb's / menu, or type any name), an emoji, a label, Insert or Send, and optional arguments. Reorder or delete chips in the same list. The list applies to all projects.

Good to know

Requires bb 0.49 or later. A chip is disabled, with a tooltip, when its skill is not available for the thread's provider. Chips are not shown in the editor for queued messages. No account, network service or API key: your chips are stored by the plugin on your bb server.

More from JonniK

Bang ShellRun a shell command from a thread's composer and hand the agent the command and its output in one message. Use it when the agent's sandbox or permission mode blocks a command that needs your secrets or access: the agent proposes it, you run it, and the agent only sees the output. Send with Mod+Alt+Enter or Send menu → Run in terminal; the command runs once in the thread's own environment, on whichever machine the session uses, local or remote. You can also highlight a command in an agent's answer and pick Run in terminal next to Add to chat. Fenced shell code blocks in an answer also get a one-click Run in terminal button; python blocks get it once you turn on the runPythonBlocks setting. The message waits in the queue while the command runs, then reaches the agent as a sh block and an output block, so its next answer starts from the real result. Commands that outlast the wait (30 seconds by default) keep running in the thread's Terminal panel, and pagers are off so git log and git diff print in full. Messages from agents, other plugins and bb thread tell never run a command; commands run with your account's full rights, outside the agent's permission mode. Requires bb 0.49+ and a POSIX shell (macOS or Linux; Windows is not supported).NewBottom PanelPuts bb's App panel, with its terminal, browser tabs and previews, below the chat like an IDE, and lets you resize it by dragging the divider. Select text in the terminal and press Cmd+L (Ctrl+L on Windows and Linux) to drop it into the chat composer without sending it, also on non-Latin layouts. One header button switches back to the native right panel. Needs no account or external service.NewSession MRsShows the merge and pull requests a thread opened, with live state and pipeline status, in the thread context card and Info tab. It finds each GitLab MR or GitHub PR that the thread's own commands created (glab mr create, gh pr create, git push -o merge_request.create), lists it with a Draft, Open, Merged or Closed chip and a pass, fail or running pipeline mark, and opens it on click. Rows refresh every minute and from a refresh button; agents get bb session-mrs list and bb session-mrs status <url>. Read-only: it needs glab and/or gh logged in on the machine that runs the BB server.New

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