A plugin for shipping software with Claude Code, Codex, and Cursor

Trust what your AI ships.

Let AI build more of your software. Forge’s workflows carry it through every step, prove it works, and bring you in when it matters.

Start free →
Free for individuals. Start on your own; bring your team later. · Install the plugin →

Same AI, same ticket. The workflow is the difference.

Inside the AI tools you already use
Works with the skills you already have
Proof of what ran and who signed off
Who it’s for

For anyone
building with AI.

On your own, on a product team, or in a company without engineers. Forge works the same way; what changes is where you start.

Solo builder

“I built the feature. What should I check before I ship?”

Launch without fear and change it without breaking it. Forge checks your work before you ship and shows what passed and what didn’t.

  • Say what done means
  • Forge runs the checks in your AI tool
  • See what was checked, and what wasn’t

Product or engineering team

“AI doubled our pull requests. Our reviewers didn’t double.”

Ship at AI speed and keep review and production calm. Changes reach review already checked, a person signs off where you choose, and you can show what each ticket cost.

  • Checks before review, not after
  • A sign-off where it matters
  • Checks and sign-offs on every ticket

Building without engineers

“Our ops team built a tool with AI. Can we run the business on it?”

Build the tools your team needs and ship them with confidence. Forge checks each change, asks before anything risky, and ends with a recap of what was checked.

  • Say what the tool should do
  • Checks on every change
  • A recap you can share with IT
Why Forge

AI changed how fast software gets written.
Checking it hasn’t caught up.

Google’s DORA research finds that nine in ten developers now use AI, and that software delivery has grown less stable as it spread. The teams pulling ahead check AI work as fast as they produce it. The rest find out in review queues, incidents, and bills.

Review becomes the bottleneck.

AI multiplies pull requests, and every one still waits for a person.

With ForgeChanges arrive with the plan, the test results, and a first review attached.

“Almost right” ships.

AI code looks right at a glance, and nothing stops it from shipping.

With ForgeTests, the security pass, and review run as steps in your workflows, using the skills you already have.

Nobody can say who approved it.

What was decided and checked disappears with the chat.

With ForgeA person signs off where you choose, and the decision is recorded on the ticket.

AI bills climb with no ceiling.

Fetching a ticket and designing a fix run on the same top model.

With ForgeEach step uses the model it needs, and you see what every workflow and ticket cost, in Claude Code and Codex.

Google’s DORA research puts it this way — AI “magnifies the strengths of high-performing organizations and the dysfunctions of struggling ones.”

Built to fit, not replace
Your rules stay exactly as they are
CLAUDE.md, AGENTS.md, and .cursorrules keep governing how the AI writes code. Forge uses them inside its workflow steps and adds the shared context, the approval points, and the record.
Works with the tools you already use
Your AI coding tools, plus any client that supports MCP, the open Model Context Protocol. Switch tools anytime; your workflows stay in Forge.
Builds on the skills you already have
Forge surfaces the skills you already have at the right step, and lets admins mark the critical ones as required, so every run asks for them.
See how Forge works with skills →
Your AI tool handles the code
Your AI tool reads and edits code with its existing access. Forge guides the work using context your tool sends it. That context may include code excerpts and may be saved for future workflows.
Privacy details →
Workflows

Workflows for shipping software.
Every step, every time.

Forge’s built-in workflows cover the software lifecycle, from a bug report to a release. A workflow sets the order, makes sure the checks run, and calls on the skills you already have in your AI tool where they fit.

Skills in your AI tool bring the know-how.

Instructions, tools, and expertise that live in your AI tool. Your AI reads them and decides when to use them. A skill can hold a whole procedure.

Code reviewSecurity reviewTest generation

Forge workflows hold the process.

A workflow sets the steps, hands them to your AI tool one at a time, asks for the relevant skills, and pauses where a person signs off.

Step orderRun stateApprovalsWork record
See how Forge works with skills →
How It Works

Brief. Check.
Decide. Record.

Forge holds the workflow and gives your AI tool one step at a time. Four things happen on every run.

Your workflows · standards
your standards flow down
Forge
brief · check · decide · record
workflow runsthe record
Claude Code Codex Cursor

Set it up once. It applies in every tool below.

1
Brief — the AI starts with your context
Each step starts with your requirements, architecture, and standards, so nobody re-explains them.
2
Check — the right skills at the right step
Tests, lint, dependency audits, and review run as steps, so almost-right work is flagged before it ships.
3
Decide — people stay in control
A person signs off only where it matters, such as before a write, a merge, or a release. Everything else keeps moving.
4
Record — results stay with the work
What was checked and who decided stay on the ticket. Estimated cost shows in your dashboard.
From a sentence to a workflow

Say what you need.
Forge takes it from there.

You don’t need to know the workflows by name. Say what you need in your own words, at the start of a session or partway through one.

You sayforge, make team invitations expire after 7 days
When something needs to change
Make a change with a plan

Describe the change, with or without a ticket. Forge proposes the steps before anything runs.

  • An agreed approach
  • The change
  • A recap of what ran
You sayforge, what did we just build?
After a build
Explain what changed

Get a recap of what you built, grounded in your changes and tests.

  • What you set out to do
  • What the tests verify
  • The one gap that matters
You sayforge, review the PR for PROJ-412
Before a merge
Get a structured review

Check the change against requirements, tests, and team standards.

  • Findings
  • Coverage gaps
  • Next actions
You sayforge, triage the comments on PROJ-412
When feedback arrives
Catch up on comments

Find what still needs attention across the ticket and the pull request.

  • Outstanding feedback
  • Ready to discuss or address
What Forge does with it
Runs a workflow you already have

Forge picks from the workflows you have switched on. If several fit, it asks which one.

See the built-in workflows →
Works out an approach for this task

Nothing fits? Forge proposes the steps for this one task and runs them once you confirm. Every step that changes something asks first.

Or build your own workflow →
Examples

See what a run
leaves behind.

Built with Forge We build Forge with Forge Every change to Forge is written by AI, proven by Forge, and signed off by a person. We do it in Claude Code, Codex, and Cursor, the tools Forge runs in.
In practice One feature, from idea to reviewed pull request Each person reaches for the right workflow, and every check and sign-off lands on the ticket. Follow the feature → For teams One process and one record for the whole team A map of where AI already does the work on your team, shared workflows with approval points, and a dashboard of the work. See how teams use Forge → Cost control Top models where they matter What AI cost per workflow and per ticket, and a model tier for every step. See Token Intelligence →
Get started

Install, then
start with a task.

Start on your own with a free account and one task.

Three steps to your first workflow
1
Install in your AI tool. Choose Claude Code, Codex, or Cursor. Follow your tool’s plugin instructions and sign in.
→
2
Start with a task. Say forge, and what you need. Built-in workflows start switched off, so the first time, Forge offers to switch on the one that fits and run it.
→
3
Get your first result. Review a PR, recap your work, or plan a change. Leave with something you can use.
Setting up for a team? An admin says forge, help our team get set up, and guided setup recommends the workflows to switch on.
No Jira, Linear, or Notion connected? Reviewing a pull request, fixing a bug, and recapping your work all run without one, and results are handed to you to paste. Workflows built on a ticket, such as breaking down a feature, say so before they start. Full install guide →
Start free →
Pricing

Start free.
Bring your team when you’re ready.

Free for individuals, forever. During beta, Team features are free, and you can request seats for your teammates. Business follows when you need enterprise security and compliance.

Individual
Freeforever

Checks and a record for your own AI work, inside the tools you already use.

What's included
✓Works with Claude Code, Codex, Cursor & any MCP tool
✓Built-in workflows
✓Workflow configuration
✓Your existing rules and skills
✓Model routing on supported tools
✓Basic analytics and audit history
Beta
Team
$0 per month Normally fifty dollars per month. Free while Forge is in beta.

Shared workflows and visibility for up to 10 members.

Everything in Free, plus
✓Up to 10 members
✓Shared workflows
✓Roles & permissions
✓Organization-wide analytics
✓Token Intelligence

During beta, Team features are free and each account starts with one seat. Request more from your dashboard when you’re ready to add teammates. Team is $50 per month once beta ends. No commitment, cancel anytime.

Business
Coming Soon

For organizations with broader rollout and support needs.

Everything in Team, plus
✓Unlimited members
✓Enterprise SSO
✓Enhanced roles & permissions
✓Priority support
✓Planned compliance capabilities

Interested in early access? Talk to us →

Start free →

Forge runs inside your existing AI tools. Model routing and token measurement depend on the tool. Cost estimates use recorded tokens and published model rates; they may differ from your subscription bill.

Common questions

What to expect
before your first run.

A few details before your first workflow. Read all frequently asked questions →

Your AI tool reads and changes code using its existing access. Forge supplies workflow instructions; its service does not directly access your repository, CI/CD, or production. Your tool handles your keys; Forge doesn't ask for them. We do not use your data to train AI models. Context your tool sends may include code excerpts and may be saved for future workflows. Read the privacy details →
Workflows run in Claude Code, Codex, Cursor, and compatible MCP clients. The dedicated plugins add guardrails: file edits and writes to connected tools wait while a question or an approval is open. Model routing works in Claude Code and Codex. Token usage is measured in Claude Code and supported Codex versions, and not in Cursor. Compare the tools →
No. Reviewing a pull request, fixing a bug, and recapping your work all run without one, and results are handed to you to paste. Workflows built on a ticket, such as breaking down a feature, say so before they start. Connect one through your AI tool when you want workflow results written to the ticket.
No. Claude Code’s dynamic workflows fan one large job out to many agents. A Forge workflow walks one job through steps and pauses for people to sign off. They solve different problems, and you can use both.
Use them. Forge works across Claude Code, Codex, and Cursor, puts a sign-off where it matters, shows what runs cost in Claude Code and Codex, and keeps one record of what happened.
No. AI output varies with the model, the context, and the task. Forge makes the process repeatable and shows the checks and decisions behind a result.
Today, yes. Forge is built for shipping software: code changes, reviews, and releases. It doesn’t check reports, spreadsheets, or other non-code work yet.
A skill teaches your AI how to do something, and the AI decides when to use it. A workflow is the process itself: Forge holds the steps, hands them over one at a time, stops where a person signs off, and keeps a record. Workflows run your skills, so you keep both. See how Forge works with skills →
No. One person can install Forge, set it up, and run it. Team features are there when you add people.
Install the plugin in your AI tool, sign in, and ask Forge for what you need. Forge offers to switch on the workflow that fits, you say yes once, and it runs on your real task. A team admin can run guided setup to switch on a recommended set. See three ways to start →

Start with one task.
Ship it with proof.

Install Forge in your AI tool and start with one real task. Free for individuals; your tools, rules, and skills stay with you.

Start free → See how to install

We build Forge with Forge, in Claude Code, Codex, and Cursor.