FFORGE
Open Forge
FORGE DOCS

One outcome in. Verified software out.

Forge hides model and agent complexity by default. Open a project, describe the outcome, review the evidence.

Quick start

  1. Open Forge Desktop or the web workspace.
  2. Create or open a project.
  3. Describe what you want in plain language.
  4. Forge understands, plans, builds, tests, fixes and verifies.
  5. Review changes and evidence before accepting.

Desktop

The desktop wrapper uses an isolated renderer and explicit native permissions. Local folder selection and indexing happen through the desktop bridge; the folder picker does not silently upload source.

Desktop downloads

CLI

python forge_cli.py --json plan "Fix checkout and add tests"
python forge_cli.py --json index ./my-project
python forge_cli.py --json search ./my-project checkout
python forge_cli.py --json snapshot ./my-project --store .forge-snapshots
python forge_cli.py --json verify ./my-project -- pytest -q

Verified builds

“Verified” means the required checks configured for the task passed. Forge does not use the badge for untested code or a generation-only result.

MCP & plugins

Plugins are deny-by-default. Owners/Admins grant explicit scopes, and workspace policy can reduce the allowed scope set further.

Teams & roles

Owner/Admin: workspace policy, plugins, audit and team administration. Developer: project and task changes. Customer/Viewer: read-only review.