forge

/forge

Input: $ARGUMENTS. Obey CLAUDE.md (project isolation + honesty + no fake claims). Work only in this project folder.

Sub-commands & natural-language triggers (check $ARGUMENTS first)

Also trigger on plain language: "use Forge system", "gebruik Forge systeem", "start Forge dashboard", "open Forge dashboard", "gebruik forge voor dit project". Settings phrases ("instellingen", "settings", "zet … aan/uit/op N%") go to config below; "hoe vraag ik Forge iets" / "help me ask" goes to help me ask below.

• dashboard / start Forge dashboard → use the active project folder (the cwd; ask only if it is genuinely ambiguous, never a routine stop-and-confirm), then find the Command Center — the ONE dashboard for every project (owner decision 2026-07-31; it auto-discovers projects, so it does not need to live in THIS folder): first health-check http://127.0.0.1:4100/api/health (or CC_PORT if the owner set one) — already answering means this project is already covered, so start nothing else; otherwise (1) if command-center/gateway/bin.mjs exists in this project, that IS the Command Center home, else (1b) check the installer's shared central copy at ~/.claude/forge/template/command-center/gateway/bin.mjs (v2.9.0) — whichever copy is found: if its dashboard/dist is missing, build it yourself (npm ci inside command-center/dashboard when package-lock.json exists, else npm install, then npm run build) — never print a build command for the user; prefer the supervisor for long sessions (node command-center/gateway/supervisor.mjs — auto-restarts the gateway) or start the gateway directly (node command-center/gateway/bin.mjs, port 4100); (2) neither copy exists — say so in one line naming the installer for this OS (install.ps1/install.sh) and continue. Either way: health-check http://127.0.0.1:4100/api/health and report http://127.0.0.1:4100 as the dashboard URL — never claim it is running unless that check passed; never fake a start. Do NOT try to fall back to the old per-project Control Center — .claude/forge-dashboard/server.cjs was REMOVED in v2.9.0 (not just retired — the file and its UI no longer exist, so there is no start route at all); only log-event.cjs in that directory stays in active service as the per-project run-event writer, completely unchanged. If no Command Center is reachable anywhere, say so honestly in one line (with the expected URL) and continue — Forge starts what it can itself and never hands the user a command to type. The usage guard is not started by this sub-command — BUILD BY DEFAULT starts it when config usage-guard is on (the tool prints its own disclosure on a real start).
• config / "instellingen" / "settings" / "zet aan|uit|op N%" / "vraag me niet meer bij elke fase" / "interview mode aan" / "codex review uit" → the owner's settings: every Forge feature is ON by default, and this lists or changes any of them in one command. Map the phrase to a key yourself — node .claude/forge-bin/forge-config.cjs parse "<sentence>" names the exact set it would run; when it says "No setting recognised" or exits 3, map it from the schema aliases in .claude/config/orchestration/FORGE_CONFIG_SCHEMA.json or offer its candidates as options ("vraag me niet meer bij elke fase" → set autonomy continue-within-mission + set start-gate off). Then run the CLI yourself — node .claude/forge-bin/forge-config.cjs list|get <key>|set <key> <value>|unset <key>|reset|explain <key> — never edit FORGE_CONFIG.json by hand and never tell the user to run it. Repeat the tool's OK line verbatim; for list, print the tool's own table in the owner's language (--lang nl|en; add --ascii when the output lands in Windows cmd). Add one plain line on what changed and when it takes effect: a usage-guard key reaches the running guard only after a restart, so run node .claude/forge-bin/usage-guard.cjs stop and then start yourself right away (only stop when it was switched off); every other key applies from the next step. reset without --yes exits 3 → ask once ("Alles terug naar de standaard?") and rerun with --yes; a hard gate is locked (exit 3) — say in one line that hard gates cannot be switched off.
• help me ask / "hoe vraag ik Forge iets" / "hoe moet ik dit vragen" → show .claude/skills/forge-prompt-coach/references/HOW-TO-ASK.md (the Dutch part first, then English) — just that file, never a lecture.
• start → same as dashboard, then begin a new run (steps 0–1 below).
• interview → the full intake questionnaire, one question at a time (forge-intake skill §Iteratieve intake). By default /forge <goal> answers the intake itself; this is the opt-in for owners who want to be asked.
• propose-skill / approve-skill <name> --owner-approval <token> → node .claude/forge-bin/forge-genesis.cjs propose --gap "<x>" --evidence <file> stages a skill proposal under .claude/forge-genesis-staging/; approve (owner token required) promotes it — never automatic. (Advertised by forge-core since v8.1 but had no entry here; wired 2026-09-23 after an external audit, together with the four below.)
• tournament / secondbrain / codemodel / briefing <run_id> → best-of-N variant scoring, a read-only cross-project portfolio strategist, the incremental repo index, and the overnight-run morning briefing; each ships in forge-bin/ and prints usage on --help. Read .claude/docs/forge-reference/tournament-secondbrain-codemodel-briefing.md first.
• use / use Forge system / gebruik Forge systeem → load project memory/profile; if Forge isn't installed in this folder, install it yourself exactly like the bare-folder step in BUILD BY DEFAULT (or say in one line that Forge is not installed on this machine when its template is absent too); start the dashboard yourself as in dashboard above (or say in one line that it is not installed here); then continue the task via the flow below.
• status → node .claude/forge-bin/forge-runinfo.cjs status (or the forge-status.* wrapper): reads .claude/FORGE_MEMORY.md + newest .claude/forge-runs/*/run.json + a short-timeout health-check of the Command Center; summarize project status, latest run, and dashboard reachability.
• runs → list THIS project's .claude/forge-runs/*/ newest-first.
• resume <run_id> (WAVE D) → a session/usage limit killed a swarm mid-run; reconcile that run's manifest purely from its logged events and re-dispatch only the still-unfinished work packages, never a fabricated "done". Read .claude/docs/forge-reference/resume.md first (it also covers the required arm-manifest step and the exit codes).
• open-report → print THIS project's newest .claude/forge-runs/*/final-report.md.
• learn (WAVE F, opt-in, read-only) → cross-project learning harvest: reads OTHER Forge projects' memory files (never writes to them) and stores real, evidenced, secret-redacted lines into THIS project's reserved global lesson namespace. Explicit discovery only — nothing is scanned unless told to. Read .claude/docs/forge-reference/learn-harvest.md first.
• remember <text> / "onthoud dat …" (WAVE B / B4) → promote an explicit owner instruction into a real, ACTIVE standing rule: node .claude/forge-bin/forge-standing.cjs remember "<text>" [--scope <scope>] [--trigger always|domain|glob|on-request] [--domain <domain>] [--glob <glob>] [--topic <topic>]. This is the ONLY sanctioned path that writes a new status:"active" rule — it stamps source:"owner /forge remember" (never a fabricated/inferred source) and can never mint a new cannot_override_core rule. Report the written rule id + text back to the owner.
• snapshot (owner request 2026-07-29, .claude/skills/forge-snapshot/SKILL.md) → manual/phase-boundary context-continuity snapshot: node .claude/forge-bin/forge-snapshot.cjs write --reason phase regenerates .claude/FORGE_SNAPSHOT.md from real sources (memory/task-history/work-packages/decisions/git/latest run events/doctor) — Mission preserved verbatim, every other section re-derived fresh, never a fabricated context percentage. This is also fired automatically by the wired PreCompact (matchers manual+auto) hook and re-injected on the following SessionStart (matcher compact) — see HOOKS_OPT_IN.md section 4 for the live wiring record. node .claude/forge-bin/forge-snapshot.cjs check --max-age-hours <n> reports staleness.