bc/>
DocsContact

Guide to bc v2

bc is a CLI-first AI agent orchestration system. The TUI (bc home) is a navigational dashboard designed for fast, conflict-free multi-agent work.

Quick Start

Initialize your workspace and start the core engine in seconds.

# Initialize a workspace
bc init

# Start the root agent + core orchestration
bc up

# Open TUI dashboard
bc home

# Stop all agents and processes
bc down

Core Concepts

Root Singleton

The Root agent owns the main branch and serves as the primary gateway for all merges and team creation.

Dual Queues

Every agent manages their own work queue (incoming tasks) and merge queue (proposed work from children).

Completion Semantics

Tasks are only considered "done" once they have been successfully merged into the target branch.

Persistent Memory

Agents accumulate project-specific context and experiences over time, using mem0 for persistent retrieval.

Agent Commands

Command
Description
bc agent create <name> --role <role>
Create a specialist agent (engineer, qa, manager, etc.).
bc agent list
List all active agents and their current states.
bc agent peek <name>
Stream live output from a specific agent's terminal.
bc agent attach <name>
Gain interactive control over an agent's tmux session.
bc agent send <name> <msg>
Directly message or assign an ad-hoc task to an agent.

Queue Management

Command
Description
bc queue work
View tasks assigned to you by your parent agent.
bc queue merge
Review incoming merge requests from your child agents.
bc queue submit <branch> --to <name>
Submit your work for review to a superior agent.
bc queue merge approve <branch>
Approve a request and automatically merge the code.
bc queue merge reject <branch>
Reject a merge to send it back to the owner for fixes.

Communication & Memory

Command
Description
bc channel send #name <msg>
Broadcast a message to an agent-wide channel.
bc memory show <agent>
Display a summary of an agent's accumulated knowledge.
bc memory search <agent> <query>
Semantic search through an agent's past experiences.

Configuration

Workspaces are managed via a central .bc/config.toml file.
[workspace]
name = "bc-infra"

[tools.claude]
command = "claude --dangerously-skip-permissions"

[memory]
backend = "mem0"
path = ".bc/memory"

[channels]
default = ["general", "engineering", "coordination"]