forge

Forge

A deterministic build-and-repair harness OS for long-running coding work.

Forge gives coding agents phase discipline, ownership, continuable state, and guarded verification routing — so work that spans sessions, days, or interruptions doesn't fall apart.

The problem

Coding agents are fast but forgetful. On long-running tasks they lose track of what was decided, who owns what, and where things broke. When a session ends, context disappears. When it resumes, you re-explain everything.

Forge fixes this by writing project state to files — not chat history — and structuring work into phases with explicit gates, decision traces, and verification surfaces, so every session picks up exactly where the last one stopped.

Who this is for

• Multi-session projects where context loss is the bottleneck
• Teams that need an audit trail of specs, designs, and decisions
• Build or repair work that benefits from phase gates instead of open-ended prompting
• Parallel development where lane ownership and merge order matter

Core UX

forge info — see where you are

Shows current phase, what's blocking, and what to do next. One glance, not a wall of fields.

Internally this is backed by node scripts/forge-status.mjs, so the compact dashboard stays consistent with the runtime's canonical next_action.

Forge: my-saas-app (build)
Phase 4/9 — develop
████████████░░░░ 55%

Next action: Finish lane auth-api — JWT middleware done, testing refresh token flow
Active: auth-api, payment-ui. Blocked: db-schema (waiting on contract review)

Lanes: 2/5 done, 1 blocked
Issues: 1 blocker, 0 major, 2 minor
Tag: forge/v1-design

forge continue — restore saved state and keep going

Restores saved workflow state from .forge/ — phase, lane ownership, blockers, handoff notes — and routes to the most actionable point. No re-prompting, no re-explaining what you were doing.

When using separate CLIs such as Codex CLI and Claude CLI, resume explicitly with forge continue from either host against the same repository checkout. The decision comes from shared .forge/ state; only the host automation depth differs.

Forge: my-saas-app
Phase 4/9 — develop
3 lanes active, 1 blocked (auth waiting on DB schema)

Next action: Finish lane auth-api — JWT middleware done, testing refresh token flow

It picks the right entry point automatically:

• Blocker that needs your input? Surfaces that first.
• Internal blocker? Routes to the owning team.
• Analysis is stale? Refreshes analysis before phase work continues.
• Active lane with handoff notes? Loads that lane's worktree and task context.
• None of the above? Falls back to the current phase skill.

forge analyze — map impact before you touch code

Runs Forge's Analyst flow to produce a durable codebase analysis artifact for the active project. This is especially useful before design on existing code, before lane splitting, and before risky fixes.

Typical uses:

• architecture mapping for an existing codebase
• impact analysis for a target file/module/symbol
• dependency tracing before a fix
• quality/risk scanning before review

forge eval — turn a run into a scorecard

Compares baseline vs harness runs and emits both machine-readable JSON and a markdown report under .forge/eval/. If you do not provide a harness summary, Forge derives one from the current runtime, status, traceability, and delivery artifacts.

Typical uses:

• capture a Codex or Claude smoke run as an evidence artifact
• compare with/without-Forge outcomes for the same task
• append lightweight product proof to .forge/events/eval.jsonl

forge analytics — inspect the artifact trail

Summarizes .forge/events/, .forge/eval/, .forge/evidence/, and .forge/delivery-report/ without changing runtime state.

forge verification — inspect the latest verification artifact

Shows the latest durable verification selection/result written by Forge's verification flow.

Runtime controls

Forge now supports a few lightweight runtime controls inspired by ECC-style operational guardrails:

• FORGE_HOOK_PROFILE=minimal|standard|strict
• FORGE_DISABLED_HOOKS=hook-a,hook-b
• FORGE_STOP_BATCH_CHECKS=0 to disable Stop-time batch validation
• FORGE_PACKAGE_MANAGER=npm|pnpm|yarn|bun to override auto-detection

forge — start a new project or fix an existing one

Forge detects whether you're building something new or fixing something broken, and routes accordingly.

Product thesis

Forge is a deterministic harness OS for engineering teams.

That means Forge optimizes first for:

• repeatable routing and gate decisions
• explicit verification state
• recoverable failure loops
• durable artifacts instead of chat-only context
• honest bounded degraded behavior across hosts

It does not optimize first for giant skill catalogs or toolbox breadth.

Build and repair workflows