Forge User Manual

Chapter 29

Forge CLI

FREEAvailable

Supported Forge CLI commands — Ready vs Planned.

What it is

The Forge CLI manages identity, sync, and Agent helpers from a terminal.

Only Ready commands are active. Planned commands are labeled Future / Planned in the live command registry.

How to use it

See the live command list embedded in Help / Terminal chapter data (forge status, forge push, forge pull, forge init, forge login, …).

Do not treat Planned rows as shipping features.

Command registry

  • forge .Launch Forge Desktop for the current path.Ready
  • forge agent knowsInventory known / partial / stale / not-indexed systems from memory and index.Ready
  • forge agent refreshRescan the workspace and upsert changed/new/deleted eligible files into the Agent source index (symbols, imports, freshness).Ready
  • forge agent reindexAlias for forge agent refresh — refresh the Agent source index from disk.Ready
  • forge agent statusShow index coverage, memory counts, git/diagnostics awareness for the active project.Ready
  • forge agent whyShow retrieved context provenance for the most recent Agent answer (not chain-of-thought).Ready
  • forge auth statusShow authenticated Forge account and device (no token).Ready
  • forge commandsShow every Forge command by category with ready/planned status.Ready
  • forge designSearch learned capabilities from past projects and rank by relevance for reuse.Ready
  • forge env checkVerify secret access / presence without dumping values.Ready
  • forge env listList Forge Secrets for the project environment.Ready
  • forge env removeDelete a secret from the project environment.Ready
  • forge env setCreate or update a secret value.Ready
  • forge initExisting project: bind Forge identity. Empty folder: optional scaffold from New Project Defaults (set up once and forget about it).Ready
  • forge inspect architectureRun Architecture Invariants analysis for the project (health score + evidence).Ready
  • forge learn capabilitiesList all learned capabilities across your projects with optional filtering.Ready
  • forge learn inspectDetailed view of learned capabilities and architecture rules for the current project.Ready
  • forge learn rebuildRe-extract reusable capabilities from the current project index. Does not refresh the Agent source index.Ready
  • forge learn statusShow current project learning status, capability count, and recent learning events.Ready
  • forge library addAdd one exact project directory to Forge Library (no child discovery).Ready
  • forge library importScan a parent folder for projects and bulk-add new ones to Forge Library (preview first; --yes / --dry-run).Ready
  • forge loginDevice authorization login (browser approval). Optional --link CODE or --status.Ready
  • forge logoutRevoke and clear local CLI device credential.Ready
  • forge modesPrint the Forge Modes catalog and readiness.Ready
  • forge pairDevice-scoped Mobile ↔ Desktop trust. Projects bind or Send to Desktop separately.Ready
  • forge presetShow, update, delete, apply, export, or import project presets. forge set captures; forge run preset applies.Ready
  • forge presetsList saved project presets and legacy stack presets (~/.config/forge/presets).Ready
  • forge pullApply cloud tip locally and verify baseline so pulled files are not re-detected as local edits.Ready
  • forge pushUpload delta (or chunked) tip changes and create the next immutable revision.Ready
  • forge runCreate a new project with a stable Forge kind (native / next / react / preset), then bind identity, isolate workspace state, and open Desktop.Ready
  • forge sendCreate/bind the current Mobile project on a paired Desktop (UI: Send to Desktop).Ready
  • forge setCapture the current project as a portable preset manifest (files + packages + scripts). Never stores secrets or node_modules.Ready
  • forge statusShow cloud vs local revision and local tip changes.Ready
  • forge syncMulti-device sync status; clean auto-pull when preference allows.Ready
  • forge <mode>Open a hard-coded Mode Preview workspace (does not activate unfinished runtimes).Planned
  • forge bind <projectId>Restore an existing Forge project identity onto this folder (dedicated verb reserved).Planned
  • forge castReserved Git Bridge verb — not fully functional yet.Planned
  • forge fuseReserved Git Bridge verb — not fully functional yet.Planned
  • forge mineReserved Git Bridge verb — not fully functional yet.Planned
  • forge smithConstruct from an approved Forge design plan. Full autonomous smith continues to roll out.Planned
  • forge temperReserved Git Bridge verb — not fully functional yet.Planned