The One Forge

What Ships

Repo-aware build and debug flows that clone a GitLab project, inspect conventions, and generate a merge-request-ready diff

Verification gates for generated files, dependency repair, build checks, delivery guard, and preview readiness

Run history with logs, cost breakdowns, approvals, rejection handling, and shareable delivery summaries

Why It Feels Safe

Human approval before plan execution and before merge-request publish

Measured token/cost reporting with model, backend, and pricing-source details

Atomic run claiming, ownership checks, persisted handoff data, and path containment for generated files

Best Outcome

Use this flow when you want something you can demo, hand off, or iterate on quickly instead of staring at a blank repo.

New Project

Pick a template, describe the target outcome, and Forge will shape a runnable delivery package around it.

Template Gallery

Try one of these prompts

Saved team-ready templates

Prompt Library

Deliverables

Code, generated files, setup guidance, and a project history your team can revisit.

Trust Layer

Verification, retries, and observability make the output feel reviewable instead of mysterious.

Best Fit

Best for prototypes, client work, internal tools, debugging, deployment packs, and launch-ready starters.

Project Name

Pipeline Mode

Create a new project from scratch

Describe the outcome you want

Tip: mention the target user, must-have screens or endpoints, deployment target, and what counts as done.

Upload existing project (ZIP or folder)

Optional — gives the forge your existing code as context

Full auto — no approvals needed

Auto-pilot