Skip to main content
The forge command surface is defined as data (src/commands.js) and reconciled against the docs by forge docs check, so a command can’t ship or disappear without the docs noticing. Commands are organized into five groups.

Core

Bootstrap and maintain: init, sync, doctor, catalog, docs, update.

Memory

Cross-session and team memory: cortex, recall, remember, brain, ledger, reuse, handoff, decide.

Substrate

The pre-action gate and its stages: substrate, preflight, route, impact, scope, context, anchor, diagnose, imagine, lean.

Quality

Verification and safety: verify, scan, spec, taste, uicheck, harden.

Config

Providers, cost, dashboards, brand, atlas, stack: config, cost, dash, brand, atlas, stack.

​
Conventions

  • Advisory by default. Set FORGE_ENFORCE=1 to turn the substrate into a hard block on the strongest signals (vacuous prompt, un-assemblable required context, blast radius over the default 25-file threshold).
  • Quiet by default. The per-command Forge <cmd> — … title is branding chrome behind --verbose / FORGE_VERBOSE; a command emits its result first.
  • Pipe-friendly output. Plain text when piped; on a TTY it adds brand-palette color and confidence meters. NO_COLOR turns color off, FORCE_COLOR=1 forces it on.
  • --json is available on the substrate and most analysis commands for scripting.
Run forge --help for the always-current list, or forge catalog for the Start-Here index of every tool, crew, and guard with a one-line why.

​
New in v0.19+

Several commands and flags are landing in the v0.19 line. They are documented in their group pages and flagged inline: