bb-cli

Controls bb threads, projects, machines, and environments through the bb command-line interface.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/celeroncoder/skills --skill bb-cli-celeroncoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bb-cli
Source: https://github.com/celeroncoder/skills/tree/main/bb-cli
Command: npx skills add https://github.com/celeroncoder/skills --skill bb-cli-celeroncoder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-agent work in bb requires knowing dozens of CLI commands for threads, projects, machines, environments, and settings; this Skill gives an agent the operational knowledge to inspect, spawn, and orchestrate bb resources correctly without guessing flags or defaults. ## Core Features & Use Cases - Thread orchestration: Spawn, fork, steer, queue, stop, and inspect threads with explicit project, permission, visibility, and parent controls. - Project and machine management: Create projects bound to enrolled machines, register remote sources, upload attachments, and inspect provider models per machine. - Environment and diff inspection: Read environment status, branches, diffs, and pull-request state so review and fix pipelines can target the same workspace. - Use Case: An agent receives a bug report, runs bb status for context, spawns a child thread with a clear prompt and permission ceiling, waits on it with bb thread wait, then reviews the result via bb thread show --git-diff. ## Quick Start Ask the agent to check the current bb context with bb status and then spawn a new thread in your project with a prompt describing the task you want done.

Frequently Asked Questions about bb-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I spawn a new bb thread from the CLI?▼

Use bb thread spawn with --project <project-id> and --prompt describing the task. The CLI does not infer the project from context, so pass it explicitly; add --file or --image for attachments and --parent-thread to nest it under an existing thread.

How do I wait for a bb thread to finish?▼

Use bb thread wait <thread-id>, which blocks until the thread becomes idle for up to 20 minutes by default. Pass --status or --event for a different target and --timeout <seconds> to adjust the budget instead of polling with repeated status reads.

What permission modes does bb support for threads?▼

bb exposes three public permission modes: accept-edits, auto, and full. Auto is the product default, full bypasses sandbox and approvals, and a child thread can never exceed its parent's permission ceiling.

Can bb run threads on a remote machine?▼

Yes. Enroll machines from Settings → Machines, then pass --machine <id-or-name> to bb thread spawn or bb project create. Each machine has a maxPermissionMode limit that only the owner can change in the app.

Why does bb thread list not show my background worker thread?▼

Threads spawned with --visibility hidden are excluded from bb thread list by default. Pass --include-hidden to discover them; direct-ID operations like stop, show, and tell still work on hidden threads.