Extensible harness

ForgeCode

One terminal coding harness for many models, scripts, and specialist agents.

Status
Active
License
Apache-2.0
Evidence
Documented + code-verifiable, 24 sources
Product record checked
2026-07-27

At a glance

ForgeCode is an open terminal coding harness that works interactively or as a one-shot command. The audited source defines 47 provider entries spanning hosted APIs, subscription access, local endpoints, and a context engine, plus MCP, skills and delegated agents. It runs on your machine by default; its `--sandbox` option separates Git work but does not contain commands.

Good choice if

  • Vibe coders who want to keep one terminal tool while switching among subscriptions, API providers, and local models
  • People who want an interactive coding session now and repeatable one-shot scripts later
  • Power users who want reusable skills, MCP tools, semantic code search, and delegated research agents

Check before choosing

  • The `--sandbox` flag only creates a separate Git worktree and branch; commands still run on the host
  • Restricted permissions are off by default, the generated policy allows all built-in actions, and MCP tools bypass it
  • Optional semantic search uploads source chunks and embeddings to ForgeCode Services; logging out does not delete indexed data
See 1 more considerations
  • Browser work requires an external MCP server, and file undo restores one path's last snapshot rather than a project checkpoint

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Reusable skills
DocumentedProduct-supported reusable skill packagesSource · checked 2026-07-27Support does not establish portability, package quality, safety, or adoption.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Getting started

Install the binary, connect the provider you already use, and start with `forge`. Before unattended or delegated work, write restrictive permission rules and review every MCP server; use `forge -p` when you are ready to automate.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationWorkspace isolationDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible toolsDocumented mechanism, not a performance score.
  • Context & stateManaged contextDocumented mechanism, not a performance score.
  • Lifecycle & recoverySession resumeDocumented mechanism, not a performance score.
  • ObservabilityLogs/transcriptsDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsHost accessDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

4/5public artifacts present
Security policy
Not found
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Present at inspected commit
Contributor documentation
Present at inspected commit

No repository security policy was found, and project evaluation assets are not independent evidence. The contribution guide is stale and calls the code proprietary despite the root Apache-2.0 license.

Inspect commit 1ca089a52fd2d11ec3b0e84fa0eba154bbb81270, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs
Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage
  • Latest stable releasev2.13.21Released 2026-07-31; 14 stable releases in 90 daysOpen release
  • Homebrew 30d events20Formula: forgecodeOpen artifact
  • Release asset downloads121.68K371 stable releases; 2913 matched assetsOpen artifact
  • GitHub stars7.62KFull-source repository; 1.46K forksOpen artifact

Routing, package retrievals, release downloads, editor installs, and repository interest observe different populations. They are never added together and never affect capability evidence, classification, or measured results.

Interpretation rulesSignals checked

First-party evidence

Each capability claim links to the first-party record that supports it.

24 first-party sourcesProduct record checked

Additional first-party sources

24 sources
View 23 more sources