Requirements

• Bun 1.2+ — runtime for the CLI
• Node.js — for MCP servers that use node
• npm — when installing the published package or adding npm skill bundles
• Optional: parallel-cli or markdownify-mcp only when you enable those integrations

Install

Published package

npm install -g beginning-harness
bgng status

The published package includes built-in harness defaults. By default, global bgng uses that packaged harness source.

Work from a checkout

Use this mode if you want to edit the registry, maintain your own fork, add built-in skills, or develop the CLI:

git clone https://github.com/remyjkim/beginning-harness.git
cd beginning-harness
bun install
bun run bgng -- status

You can also point a global install at a checkout:

export AGENTS_REPO_ROOT=/path/to/beginning-harness
bgng status

For local development, link the package:

bun link
bgng --help

Quickstart

Start by inspecting before writing:

bgng status
bgng skills list
bgng mcp list
bgng apply --dry-run

If the dry run looks right, apply the generated state:

bgng apply

That first run gives you:

• a system overview
• the current skill inventory
• the active MCP inventory
• a planned-change preview
• an explicit apply step

Project-specific setup

For a project-specific setup, start in the project directory:

bgng init
bgng add extension parallel
bgng add skill <skill-name-or-query>
bgng add mcp <server-name>
bgng apply --dry-run
bgng apply

Non-interactive mode

For scripts and CI-style setup:

bgng init --non-interactive