Forge Wiki — ChatGPT MCP for local computer and software tasks
Forge is a local-first, permission-scoped MCP action runtime for ChatGPT and other explicitly selected external controllers. It gives ChatGPT durable execution tools for local files, Git repositories, browsers, and authorized services—without putting an additional AI agent inside Forge. The product is intentionally Direct-first: ordinary bounded work stays lightweight, while Process Runtime, Work, worktrees, scheduling, and Recovery exist for the cases that actually need lifecycle or isolation.
Get started with the latest stable version
Install Forge v1.8.1 from npm:
npm install -g @moretea-labs/forge@latest
forge setup
forge setup configure --controller chatgpt --tunnel auto
forge setup next
macOS and Linux are supported; WSL2 is the recommended Windows path. Native Windows remains a preview. For upgrades and service setup, see Installation.
Start here
- New user: Quick Start
- Installation choices: Installation
- Product model: Core Concepts
- Request-to-evidence flow: Work Lifecycle
- System boundaries: Architecture
- Runtime behavior: Runtime Architecture
- Source implementation map: Implementation
- Run and recover the service: Operations
- Computer and provider setup: Computer and Plugins · 中文教程
- Optional capabilities: Integrations
- Diagnose a problem: Troubleshooting
- Trust boundaries: Security Model
- Upgrade or publish: Releases and Upgrades
Current baseline
The normal ChatGPT connector uses a bounded 19-tool surface with five preferred facades. Small understood work can go directly from context to patch to verification. Long commands and checks use the managed Process Runtime; separate worktrees are used when concurrency or isolation actually requires them. One Canonical Forge Runtime owns active execution authority, while standalone Recovery remains an independent failure domain.
Plugin capability completeness is deliberately separate from the core Runtime baseline: a plugin can be unavailable without redefining whether repository execution, Process Runtime, or Runtime recovery is correct.
What belongs where
The Wiki explains stable concepts, architecture, implementation boundaries, and common operator decisions. Exact source contracts, compatibility matrices, tests, and incident procedures remain versioned in the repository documentation. When Wiki content and repository source disagree, the versioned repository source is authoritative.