Get it for macOS

A short spoken reaction to the messages you type to your agents, in one of sixteen roles or your own character. Sound plays on the BB server machine. Requires an audio player and provider API keys; sends message text to the configured providers.


Overview

View source

Voice reactions

An unofficial BB plugin that reacts out loud to what you type to your agents. A decision model picks a reaction, or silence, and a voice model writes and speaks one short line. Ordinary questions and instructions stay silent by default.

Choose one of sixteen characters, including a noir detective, cowboy, chef and surfer, a random role per line, or your own persona. Each built-in role selects an OpenAI voice unless you set one explicitly. A language setting can fix the spoken language; the default follows the message, while shopkeeper speaks English. Edit the reaction options to decide when it speaks. It handles human prompts, follow-ups, steers and queued messages, while ignoring agent messages and retries. One line plays at a time, with no backlog.

Requirements

  • BB 0.49.0 or later. The plugin uses experimental BB events.
  • An audio player on the server: ffplay, SoX play, aplay or paplay.
  • Provider API keys. TypeSafe and Vercel AI Gateway can decide; OpenAI Realtime can speak. OpenAI Decisions and OpenRouter decision/audio paths are implemented and tested offline, without live verification.

Sound plays on the machine running the BB server, not in the browser. With a remote server you will not hear it on your local computer.

Privacy and cost

For each human message, up to 800 characters plus up to 300 characters of reply context go to the decision provider. When it speaks, that text also goes to the voice provider. Provider charges apply. The plugin stores no message text or audio; its logs omit message text and keys.

The default OpenAI voice model, gpt-realtime, is scheduled for shutdown on January 20, 2027; choose a successor in voiceModel before then. See OpenAI deprecations.

See the README and setup guide and implementation details and known gaps.

More from Sergey Baus

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