b8e init

Write binclusive.json for the project

Arguments

Argument	Kind	Default	Description
dir	optional	.	directory to initialize (defaults to the current directory)

Options

Option	Takes	Default	Description
--extends [base]	value		scaffold an extends-based config from a shared base
--ci	boolean		also scaffold the CI workflow
--mcp	boolean		guide connecting MCP in your editor via the dashboard, and offer the Claude plugin
--all	boolean		scaffold every concern (config + CI + MCP)
--suggest	boolean		pre-fill the components map with best-guess elements to review (BINCLUSIVE_SUGGEST twin)
--force	boolean		overwrite existing files instead of preserving them (BINCLUSIVE_FORCE twin)

b8e init --help

Identical to what the terminal prints — both are rendered from the same commander definition.

Usage: b8e init [options] [dir]

Write binclusive.json for the project

Arguments:
  dir               directory to initialize (defaults to the current directory)
                    (default: ".")

Options:
  --extends [base]  scaffold an extends-based config from a shared base
  --ci              also scaffold the CI workflow
  --mcp             guide connecting MCP in your editor via the dashboard, and
                    offer the Claude plugin
  --all             scaffold every concern (config + CI + MCP)
  --suggest         pre-fill the `components` map with best-guess elements to
                    review (BINCLUSIVE_SUGGEST twin)
  --force           overwrite existing files instead of preserving them
                    (BINCLUSIVE_FORCE twin)
  -h, --help        display help for command

Concerns can be handled now with --ci/--mcp (or --all), or later with the
equivalent `b8e add ci|mcp` — the same outcome without rewriting binclusive.json.

EXAMPLES
  # Set this repository up
  $ b8e init

  # Set it up and add the CI gate in one pass
  $ b8e init --ci

INHERITED FLAGS
  --org <id|slug|name>   organization context [$BINCLUSIVE_ORG_ID]
  -y, --yes              skip all prompts and accept defaults
  --non-interactive      never prompt; fail instead of asking
  --progress <mode>      how progress is reported
  -q, --quiet            suppress progress output (same as --progress quiet)
  --no-color             disable color
  -v, --verbose          verbose diagnostics
  -V, --version          print the CLI version
  -h, --help             show help for command