Mixture of Agents

Compare two independent perspectives before your chat model acts on each request. Enable MoA per chat, share model and fallback settings across chats, and inspect each participant’s input, answer and delivery receipt from the message history. Advisors retain separate sessions, and active models can continue beyond a long-wait notice. Uses your configured BB providers and accounts, adding model calls, latency and provider usage; remote file reads require the separately installed File Gateway plugin.

Overview

View source

Compare two perspectives

Enable MoA in a new or existing chat. Two selected models analyze each message independently and in parallel. Your current chat model receives both answers, evaluates them and performs the task. Each participant keeps a separate session for that chat.

Inspect each consultation

Hover a message sent through MoA and open its small workflow icon. The modal shows the request, each advisor’s input and answer, and whether the advice reached the acting model. Separate session tabs display the native BB transcripts, including retained fallback attempts.

Control failures and waiting

Model choices, reasoning levels, fallback settings and the long-wait notice threshold are shared across chats. Enabling MoA is per chat. Choose manual retry, one reserve-model attempt, or continuation with one successful answer when the other participant fails. If neither answers, the request stays queued.

The coordinator observes BB’s native activity state. A long-wait notice does not stop an active model. Turning MoA off returns that chat to ordinary delivery; BB’s explicit Send now also bypasses consultation.

Read relevant files

Advisors can inspect local files. If the separately installed File Gateway plugin is enabled and running, they can also read remote files through its native tools or CLI, preserving the referenced machine and path. Without File Gateway, external file access is excluded from the advisor policy.

Read-only behavior is a role instruction, not a universal sandbox. Advisors inherit the original message’s BB permission mode, and File Gateway applies its own access policy.

Requirements and limits

This beta targets BB 0.43.1 and Plugin SDK 0.4.87. Use two different provider/model combinations available through your configured BB providers and accounts. Every consultation adds two model calls, latency and provider usage; fallback can add calls. No separate MoA API key or hosted service is required.

Recent conversation context is bounded, and image pixels are not automatically forwarded to advisors. Do not reload the plugin during a consultation: an interrupted request needs an explicit retry.

Documentation and source

More from Kirill Vechkasov

Agent ToolsShow which MCP servers and skills each BB machine actually has, then bring them to one catalogue and one canon. A matrix marks present, missing, and drifted configs; new servers wait for adopt, keep-local, or hide. Sync adds what is missing and never deletes on its own. The Skills tab treats ~/.agents/skills as a git canon, with fan-out into CLI homes and a version archive. Writes back up each config first; loopback paths and local secrets stay on that machine. Optional MetaMCP listing needs that gateway's API key.New CLI AgentsStart each chat with a specialist agent or selected profile instructions. Choose native Claude Code and OpenCode agents, or Codex profile developer instructions (up to 4096 characters; other profile settings are not applied), on local or enrolled remote machines. Requires BB 0.43.x on macOS or Linux and an installed, authenticated supported CLI; provider subscription limits or API charges apply.New Env CatalogStore API keys, tokens, and secrets in a single encrypted catalog across all BB sessions and machines. Securely request credentials via masked in-app modals. Agents automatically check available credentials before prompting you, and persist newly provided keys on demand. Values are encrypted at rest with AES-256-GCM and synchronized via your central BB server. Includes dedicated agent tools, a full-featured management UI with .env import/export, and terminal CLI commands.31 File GatewayBrowse files across your BB machines and FTP/SFTP website accounts, then add a native file mention to a chat so the agent opens the correct source and path. Read text or download files without exposing account passwords to agents. Requires connected BB machines or reachable website accounts; macOS/Linux, read-only website access, 256 MiB between BB hosts and 32 MiB from websites. English interface with drag-to-chat mentions, hidden-file controls and native file preview.New

More in Agents & Providers 55

Add, choose, configure, route, or coordinate who runs a thread.

View all

Browser AutomationLet BB control the in-app browser and browsers on connected machines, with inline previews for headless sessions.BB660

Bots SidebarKeep specialist bots, their memory, and their conversations together across projects. Organize chats with activity-aware trees, drag-to-bot assignment, and a state editor. Route new project conversations to an owner and coordinate bots with @ mentions or attributed messages. Uses your configured BB providers with no additional service or account. Project-folder creation requires POSIX paths.

Tobias Lütke269

HandoffMoves a whole session between agents and machines in both directions: hands a bb thread's rendered transcript to another provider (optionally on another enrolled machine, carrying uncommitted work as a patch), or adopts a Claude Code, Codex, Gemini CLI or OpenCode session from your terminal as a bb thread in the same directory.

Vedran Burojević263