bb-app weekly downloads statistics

bb

bb is an agentic IDE that builds itself. It can control, customize, and automate itself, laying the groundwork for your own software factory.

This package provides the npx bb-app launcher, bundled bb CLI entry, and Node SDK export. Every surface — the web app, CLI, and HTTP API — is a first-class way to drive bb. Work runs in threads you can follow live, steer at any point, or hand off to another agent.

Note: bb is in active development. Workflows and surfaces are still evolving.

Quick Start

bb runs from npm and orchestrates coding agents you already have installed.

Prerequisites

• Node.js 22.19, 24, or 26. • Git. • At least one supported agent provider: Claude Code, Codex, Cursor via ACP, Pi, or another ACP-compatible agent.

If you already use one of these providers, bb will pick up your existing credentials. If you use multiple providers, you can mix and match per task.

Supported host environments

• macOS • Linux

Windows via Ubuntu on WSL2

Run all bb commands inside WSL2, install Node.js, Git, and your provider CLIs inside that WSL2 distro, and use Linux-style paths such as /home/me/repo or /mnt/c/Users/me/repo.

Inside WSL2, use Linux paths rather than drive-letter or UNC paths. Repos inside the WSL filesystem are recommended; /mnt/c/... is intentionally supported so you can keep an existing Windows checkout, but it is slower and less reliable for file watching.

Install and run

Then open: http://localhost:38886

To opt into the automated nightly channel:

Nightly versions are built from main and may be unstable. The nightly dist-tag moves independently of the stable latest tag.

npm 12 and later block dependency install scripts by default. bb needs those scripts to build its native add-ons (better-sqlite3, node-pty, @parcel/watcher). Without them bb stops at startup with Could not locate the bindings file. If your npm version is 12 or later, allow the scripts for the install:

Or set the policy once for all global installs:

npx bb-app@latest downloads the published bb-app package, starts the server and local host daemon, and serves the web app. It stores bb-managed state under ~/.bb/ by default. If either managed child process exits unexpectedly, the launcher restarts that child without stopping the other one. Press Ctrl+C in the terminal to stop both processes and exit with status 0.

If another live bb owns the runtime record for the same data directory and a healthy server answers on the configured local address, startup exits with status 1 without starting either child process. The existing instance keeps running. A runtime record without a healthy server does not prevent startup.

Server and host-daemon output goes directly to logs/server-stdio.log and logs/host-daemon-stdio.log under the data directory, including startup errors and console output. These files append across restarts; they are separate from the rotating application logs. The launcher prints status and log locations without forwarding service output to the terminal, so a stalled terminal cannot block service logging. To follow output with the default data directory:

Launcher status output is plain when stdout is redirected, including in CI. Set FORCE_COLOR=1 to request color or NO_COLOR=1 to disable it; NO_COLOR takes precedence. In-place progress updates require a stdout TTY.

The same output capture applies to bb-server and bb-host-daemon.

To stop a bb that runs in another terminal or in the background:

stop reads bb-app-runtime.json from the data directory, confirms that the recorded process really is that launcher, then stops it. Pass --data-dir when the bb you want to stop does not use the default ~/.bb/.

The bb command

To control bb from outside bb, open Settings → General → Command line and choose Install next to bb CLI. Threads in bb already have bb; this is for your own terminals, scripts, and agents running outside bb, such as Claude Code or Codex. bb links a launcher from ~/.bb/bin/bb into a folder on your PATH (~/.local/bin on Linux; /opt/homebrew/bin, /usr/local/bin, or ~/.local/bin on macOS). On Windows it adds ~/.bb/bin to your user PATH; open a new terminal afterwards. Remove takes it off again. bb leaves any other bb you already have in place.

From a terminal, before bb is on your PATH:

Updating from the app

When bb has an update, Settings → Updates shows an Update button (or run bb updates app apply). bb downloads the new version into ~/.bb/app-versions/, restarts into it, and reconnects the page. bb does not roll back: if the new version fails to start, run a newer release (npx bb-app@latest) or fix the cause. Later npx bb-app runs use the newer installed version; pass --bundled to run the copy npx downloaded instead. Start bb with --no-in-app-updates to turn in-app updates off.

After the server moves to another machine, the old data directory keeps server-moved.json. bb-app there starts no server: it runs this computer's host daemon against the new server address in config.json, restarting it when it exits, and answers the old server port. API requests get 410 server_moved with the new address; browser pages redirect to it for a direct address or link to it for bb connect. While a move back to this computer is in progress (server-import.json), it frees that port for the incoming server. When server-moved.json goes away, after that move completes or bb server unlock, it starts the server and co-located daemon again. bb-server exits with status 3 instead of starting, except for the incoming server of a move back.

From the app, add or open a project, start a thread, and choose the provider you want that thread to use.

CLI

The package also exposes the bb CLI for an already-running bb server:

The CLI uses the same BB_SERVER_URL and bb config resolution as the SDK. When unset, it targets the default local packaged server at http://127.0.0.1:38886.

Scripting with the SDK

The package also exposes a Node SDK for scripts that drive an already-running bb server:…

Description from the npm listing.