The AI Engineering Workbench

Make every code change understandable.

FORGE helps you understand unfamiliar codebases, map architecture, inspect change risk, review proposed patches and verify outcomes — with evidence at every step and you in control.

TYPESCRIPT TOOLING · LOCAL DASHBOARD · EXPLICIT APPROVAL · INSPECTABLE OUTPUTS
forge — engineering sessionLOCAL DEMO
01 / PROJECT INTELLIGENCE
$ forge deep ./your-project ✓ Source tree inspected ✓ TypeScript AST parsed ✓ Import relationships mapped ✓ Impact candidates collected
Architecture mapREADY
Change-risk signalsREVIEW 04
Verification history3 SAVED RUNS
Dependency assessmentREPORT-BASED
Illustrative terminal walkthroughNO LIVE SCAN
GET STARTED

Bring FORGE into your workflow.

Clone the open-source project and build it locally. Node.js 22+ required.

$git clone https://github.com/ansh44233/FORGE-ECC.git && cd FORGE-ECC && npm install && npm run build
Verified integration paths
Claude Code PROVIDER + MCPCursor MCP CLIENTMCP AVAILABLEOpenAI API AVAILABLEAnthropic API AVAILABLEGoogle AI AVAILABLEOllama AVAILABLE
UnderstandProject and codebase intelligence
VisualizeArchitecture and dependency signals
EvaluateRisk, reviews and remediation plans
VerifyChecks, history and regression signals
The FORGE platform

One workbench. A complete engineering picture.

Explore the capabilities currently documented in the FORGE repository. Each tool is designed to surface useful evidence, explain its limits and leave consequential decisions with the developer.

01 / DISCOVER
⌘

Project intelligence

Identify languages, manifests, frameworks, scripts, dependency counts and important project configuration before you start changing code.

forge inspect
02 / ARCHITECTURE
⌗

Architecture mapping

Explore source modules, import relationships, external packages, likely entry points and circular dependency groups.

forge map · forge deep
03 / CODE INTELLIGENCE
⌘

AST & symbol analysis

Parse JavaScript and TypeScript syntax to find declarations, exports, circular imports and transitive file-impact candidates.

TypeScript AST
04 / CHANGE INTELLIGENCE
⌁

Git change-risk analysis

Connect working-tree changes with downstream modules, structural hotspots, repository signals and candidate tests.

forge git · change-risk
05 / CODE REVIEW
⌕

Review history

Save review snapshots, inspect individual findings and compare reviews to understand how static findings change over time.

forge review-history
06 / PATCH SAFETY
⟐

Patch proposal validation

Check proposed unified diffs for target paths, hunk structure, line counts and source context — without applying the patch.

forge patch-check
07 / VERIFICATION
✓

Verification engine

Choose a named project script, run it deliberately and record output, exit status, duration and timestamps.

forge verify
08 / REGRESSION
↗

Regression intelligence

Compare saved verification outcomes to identify regressions, recoveries, persistent failures and stable checks.

forge regression
09 / HEALTH
◉

Engineering health score

Combine available quality, verification and dependency evidence with explicit coverage so missing evidence is not mistaken for a pass.

forge health
10 / DEPENDENCIES
⛓

Dependency & license intelligence

Inspect npm manifests and lockfiles, and import local audit/outdated reports to review vulnerability, version and license signals.

forge deps
11 / REMEDIATION
✳

Remediation planner

Prioritize dependency findings and suggest review steps. FORGE does not silently install, upgrade or remove packages.

forge remediate
12 / TIMELINE
◷

Engineering intelligence timeline

Capture local snapshots and compare architecture size, hotspot counts, quality findings and selected project signals.

forge snapshot · timeline
13 / DASHBOARD
▦

Local engineering dashboard

Bring project health, architecture, saved runs, reviews, task activity and workspace exploration into a local control center.

forge dashboard
14 / WORKSPACE
▤

Interactive workspace explorer

Browse supported project files and folders, inspect sizes and preview source or documentation in the local dashboard.

Read-only explorer
15 / ORCHESTRATION
⤢

Task & run visibility

Inspect saved orchestration runs, task activity and run details, with explicit approval controls for recorded workflow tasks.

Dashboard workflow view
16 / AI ASSISTANCE
✧

AI-assisted review

Use a configured provider for review suggestions and single-file patch proposals. Selected source context may be sent to that provider.

Optional provider setup
Inside the workbench

See the engineering, not just the slogan.

A visual preview of the core objects FORGE works with: connected modules, code signals, security checks and verification history. These panels are product illustrations, not live scan results.

FORGE / PROJECT CONTROL CENTER● LOCAL WORKSPACE PREVIEW
01 · Architecture graph
Trace the system
CLICOREDASH
Modules · imports · entry points · impact paths
02 · Code intelligence
Understand source
AST symbols · exports · dependency edges
03 · Safety signals
Review before action
✓
Advisory checks · human approval
04 · Verification
Track outcomes
Saved runs · regression comparisons
05 · The engineering loop
Discover → Map → Review → Verify
Connect repository context to deliberate engineering decisions. The live dashboard runs locally on your machine; this public preview contains no real project data.
ILLUSTRATIVE PRODUCT UI · NOT A LIVE SCANFORGE / OPEN SOURCE
A toolkit with real shape

Purpose-built tools. One connected workflow.

FORGE is more than a logo and a terminal. These are the product areas developers can explore in the repository today.

FORGE 1.0 · LIVE LOCAL DASHBOARD

Your workspace. Your control center.

The full dashboard runs on your machine and connects to the project directory you choose. It is not a mock screen and it does not upload your repository to this public website.

Launch the dashboard

git clone https://github.com/ansh44233/FORGE-ECC.git cd FORGE-ECC npm ci npm run build node dist/cli.js dashboard ./your-project

Replace ./your-project with the local project you want to inspect. Open the localhost URL printed in your terminal.

Full setup instructions ↗

What opens in the dashboard

  • Project health, stack and architecture overview
  • Agent registry, saved runs, task inspector and approval controls
  • Workflow editor and agent/skill configuration studio
  • Workspace explorer and symbol-aware code search
  • Reviews, verification history, traces and regression signals
  • Evaluations, benchmark comparisons and agent performance

Provider-backed execution still requires your own provider credentials and explicit permission configuration.

The FORGE ecosystem

Three connected layers. One engineering workflow.

A product system built around understanding repositories, guiding engineering work and verifying outcomes.

LAYER 01 · INTELLIGENCE
⌘

Codebase intelligence

Repository inspection, AST and symbol analysis, dependency relationships, architecture mapping, Git-aware impact candidates and snapshots.

CURRENT TOOLING
LAYER 02 · ENGINEERING
⌁

Planning & verification

Change-risk signals, review history, patch validation, remediation plans, named checks and regression comparisons.

CURRENT TOOLING
LAYER 03 · OPERATIONS
◉

Agent workbench

Reusable specialist workflows, agent run visibility, shared project guidance and policy-aware orchestration.

ROADMAP · NOT SHIPPED
Reusable engineering playbooks

Not just commands. Repeatable ways to work.

A proposed catalog connecting planning, implementation, review and verification. These modules are planned, not available in the current release.

PLAYBOOK 01
▤

Planner

Turn a feature request into scoped tasks, dependencies, acceptance criteria and a verification plan.

PLANNED
PLAYBOOK 02
⌕

Code reviewer

Review diffs for correctness, maintainability, security-sensitive patterns and missing tests with evidence-linked findings.

PLANNED EXPANSION
PLAYBOOK 03
✓

Test strategist

Recommend tests from changed modules and impact candidates, then track which checks actually ran.

PLANNED EXPANSION
PLAYBOOK 04
⛨

Security analyst

Auditable local review for agent configuration, risky permissions and unsafe project defaults.

PLANNED · SCOPE TBD
PLAYBOOK 05
⛓

Dependency curator

Explain outdated or vulnerable packages, compatibility concerns and human-reviewed upgrade options.

PLANNED EXPANSION
PLAYBOOK 06
↻

Learning journal

Capture recurring fixes and team conventions as reviewable guidance with provenance and confidence.

PLANNED
Product roadmap

Build the ecosystem without fake promises.

Proposed milestones inspired by the breadth of the ECC product experience. Nothing here is called shipped until code, tests and docs exist.

NOW · FOUNDATION

Stabilize the workbench

Green CI, reliable local dashboard, command discovery, docs and first-run onboarding.

NEXT · PLAYBOOKS

Skills & agent catalog

Versioned workflow packs, specialist roles, install profiles and explicit permissions.

THEN · TRUST

Security & policy review

Local configuration auditing, severity-ranked findings, policy checks and reproducible reports.

FUTURE · LEARNING

Project memory & team sync

Opt-in learning from accepted fixes, pruning controls, provenance and portable team guidance.

Interactive product tour

See how the workbench connects the dots.

Choose a stage to preview the kind of evidence and workflow FORGE brings together. This is an illustrative product tour, not a live repository scan.

F. / WORKBENCH PREVIEW● INTERACTIVE DEMO

Start with context.

Inspect the repository before making assumptions about how it works.

⌘
Project profileLanguages · scripts · manifests · dependencies
FOUND
⌗
Source inventoryRecognized files and project structure
INDEXED
◉
Scan notesLimits and unresolved evidence are visible
REVIEW
A repeatable engineering loop

From unfamiliar repo to verified change.

FORGE connects discovery, architecture, review and verification into a workflow you can inspect and repeat.

01 / UNDERSTAND

Inspect the codebase

Discover the stack, scripts, dependencies, project structure and available evidence.

02 / MAP

Trace architecture

Explore imports, symbols, hotspots and likely downstream impact before editing.

03 / PLAN

Review the change

Inspect risk signals, review findings and remediation suggestions. Decide what to accept.

04 / VERIFY

Prove the outcome

Run selected checks, save results and compare with prior verification history.

Developer control

Transparent by default. No mystery automation.

Local-first workflow

  • Analyze a project directory you choose.
  • Dashboard binds to localhost by default.
  • Saved snapshots and histories stay in the local .forge directory.
  • AI review is optional and sends selected source context to your configured provider.
  • Public site previews do not access your local source code.

Human approval stays explicit

  • Discovery does not automatically execute project scripts.
  • Verification requires you to select a named script.
  • Patch checks are dry runs; they do not apply changes.
  • Dependency remediation is a plan, not an automatic installer.
  • Risk scores are heuristics, not security guarantees or defect predictions.
Fits your workflow

Open tooling. Your machine. Your decisions.

FORGE is an independent TypeScript project with a CLI and a local dashboard. Use it against a trusted local workspace and review every suggested action.

TypeScriptNode.js 22+CLILocal dashboardGit-aware analysisnpm dependency reportsVitestMIT License
Explore the workbench

Tools for the whole change lifecycle.

From first inspection to post-change verification, FORGE keeps the evidence and the next decision in one place.

TOOL 01
⌕

Inspect & map

Profile a repository, explore source structure, imports, symbols and likely impact paths.

AVAILABLE IN CLI
TOOL 02
▦

Local control center

Review health snapshots, architecture, saved runs, task activity and a read-only workspace explorer.

AVAILABLE LOCALLY
TOOL 03
✓

Verify & compare

Run a selected project script, preserve its result and compare it with the previous recorded run.

AVAILABLE IN CLI
AI providers & editor integrations

Bring your tools. Keep your workflow.

FORGE supports provider-backed runs and exposes a local, read-only MCP tool server. Editor compatibility is through MCP configuration, not a claim of a native editor extension.

AI provider adapters

  • Claude Code CLI: local authenticated CLI adapter for proposal-only agent runs; no Anthropic API key required for this path.
  • OpenAI API: configured with an OpenAI API key or compatible endpoint.
  • Anthropic API: configured with an Anthropic API key.
  • Google AI: configured with a Google API key.
  • Ollama: local model endpoint.

Provider credentials and model access are controlled by the provider account you configure.

Provider setup guide ↗

Claude Code & Cursor through MCP

  • Claude Code: connect FORGE's local stdio MCP server or use its Claude Code CLI provider adapter.
  • Cursor: connect the same local MCP server using Cursor's project-level .cursor/mcp.json or global MCP configuration.
  • Read-only tools: project inspection, architecture mapping, code search, quality audit, Git intelligence, agent listing and review planning.
  • No native editor extension is claimed: these are documented MCP integrations.
Claude Code setup ↗ Cursor MCP docs ↗
Open source · Built in public

Make the work visible.
Help shape what comes next.

FORGE is an independent, MIT-licensed engineering workbench. Explore the implementation, inspect the roadmap, report issues and contribute improvements directly in the repository.

Simple, transparent access

Open source. No paywall.

FORGE is published under the MIT license. There are no paid tiers or hosted-service claims on this page.

COMMUNITY EDITION

$0

Use the open-source CLI and local dashboard on your own machine.

  • Project inspection and architecture analysis
  • Review, verification and regression history
  • Local engineering dashboard
  • MIT-licensed source code
Get FORGE on GitHub ↗
GET STARTED

Build it locally.

Requires Node.js 22+. Clone the repository, install dependencies and build the CLI.

git clone https://github.com/ansh44233/FORGE-ECC.git
cd FORGE-ECC
npm install
npm run build
Read setup instructions ↗
Questions

Know what you're getting.

Is the public website the actual engineering dashboard?

No. The public website explains FORGE and contains illustrative previews. The full engineering dashboard runs locally against a project you select.

Does FORGE automatically change my code?

No. Patch validation is a dry run. Remediation output is a plan. Verification runs only when you select a named script.

Does FORGE scan every programming language?

Current architecture and deep AST analysis focus on JavaScript and TypeScript. Other project signals are based on recognized manifests, files and configuration.

Does the health score prove a project is secure?

No. It is an evidence-based prioritization heuristic. Missing audit reports are marked not assessed, and a score is not a certification.

Does AI review send my code somewhere?

AI review sends selected source excerpts to the provider you configure. Review your provider's data handling terms before enabling it.

Can I use FORGE without a hosted account?

The CLI and engineering dashboard are local tools. The public Vercel site is a separate static product page.

Build with FORGE

Understand more. Change with confidence.

Explore the code, inspect the roadmap and help shape the next engineering workbench.