What Extensions Are

Extensions are named capability families that bgng can inspect, diagnose, and set up. They are distinct from skill bundles and MCP servers — an extension can combine CLI prerequisites, repo-native skills, optional MCP servers, project setup actions, and diagnostics under one user-facing name.

Inspect extension support:

bgng extensions list
bgng extensions show beads
bgng extensions status
bgng extensions doctor

Machine-readable output is available with --json.

Current Extensions

Parallel

Parallel support is CLI+skills-first. Selecting the extension for one project writes semantic config under <project>/.agents/bgng/config.json; bgng apply then derives the four Parallel skills for that project without requiring global skill curation.

Default shared skills:

• parallel-web-search
• parallel-web-extract
• parallel-deep-research
• parallel-data-enrichment

Those skills assume parallel-cli is installed and authenticated separately.

Install parallel-cli:

curl -fsSL https://parallel.ai/install.sh | bash

Authenticate:

parallel-cli login
parallel-cli auth

Preview setup:

bgng extensions setup parallel --dry-run

Enable the Parallel skills for the current project:

bgng add extension parallel

Enable project-scoped Parallel MCP as well:

bgng add extension parallel --mcp

bgng extensions status parallel and bgng extensions doctor parallel report missing CLI or MCP prerequisites.

Beads

Beads support is CLI-first and project-scoped. bgng checks for bd, reports whether the current project has .beads/, can run Beads setup recipes, and can record Beads extension config for the project.

Install bd through one of the upstream-supported paths:

brew install beads
npm install -g @beads/bd
curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash

Preview setup:

bgng extensions setup beads --dry-run

Run setup:

bgng extensions setup beads

Useful flags:

Setup never runs bd init --force or bd doctor --fix by default. Beads MCP remains optional.