The workflow layer for AI coding tools

Make your whole team ship with AI like your best engineer does.

Forge runs your team's workflow across Claude Code, Codex, and Cursor — so every session follows the same playbook, not whatever each person remembers.

Free for individuals · Works with Claude Code, Codex & Cursor

One line in your AI tool — Forge runs your team's playbook.

Why Forge

A shared workflow pays
for itself.

What Forge does

A blank prompt is a guessing game — you guess where to start, the AI guesses your architecture and standards, and the model's a guess too: frontier overpays for routine work, cheap comes back wrong and you pay again in rework. Forge runs a workflow instead — handing the AI that context up front and pinning the right model to each step. Less guessing, less rework, less spend.

2.5×
Stop paying to do it twice
Hand AI a blank prompt and it guesses your standards — and guesses wrong. The rework runs up to 2.5× the original, so Forge briefs every step with your architecture up front.
100×
Catch it in review, not production
AI ships code fast — and the bugs with it. A defect caught in review costs up to 100× less than one that reaches customers, so Forge gates every change before it ships.
90%
Pay less for what AI repeats
Forge carries your project's context from step to step, so you're not paying full price for AI to re-learn your codebase every run — the repeated context costs up to 90% less.

The numbers above are industry figures. This one's ours: Forge is built by AI and run on Forge — 96% of our context reused, not re-sent at full price.

Sources: Anthropic published pricing · IBM Systems Sciences Institute · industry rework studies.

How It Works

A workflow layer
that sits above your team's AI tools.

Your workflows · standards · SDLC
policy flows down
Forge — workflow layer
briefed · model-routed · gated · logged
workflow runsaudit trail
Claude Code Codex Cursor

Define it once — every tool below inherits your standards.

1
You define how AI works for your team
Encode your team's workflows, SDLC stages, and standards once as executable policy — not docs engineers have to remember.
2
Forge runs it for every engineer
Every session starts briefed, scoped, and gated automatically — no re-prompting, and frontier models are saved for the work that needs them. Engineers adopt it because it makes their first pass better, not because you mandated it.
3
Nothing gets lost
Every decision — AI or human — is recorded against the work item and written back to your existing tools (JIRA, Linear, Notion). The audit trail builds itself.
4
Team leads see what's actually shipping
Real-time view of time, work, and cost by SDLC stage. Board question and audit question, same record.
Built to fit, not replace
Works with any AI tool
Forge sits above Claude Code, Codex, Cursor — and whatever comes next. Switch tools anytime; your SDLC and standards stay in Forge.
Builds on the skills you already have
Forge composes with the skills your team already wrote — surfacing them at the right step, and letting leads require the critical ones.
See how Forge works with Superpowers →
Safe to roll out
Never touches your code
Forge orchestrates by sending text instructions to your AI tool — it can't read or write your repository, CI/CD, or production, and it never receives your API keys.
No proxy, nothing to train on
Forge sits beside your tools, not between them and the model — your traffic to Claude and OpenAI is unchanged. It sees workflow metadata, not your code or conversations, and never trains on your data.
See our privacy policy →
Code Quality

Quality that doesn't depend
on who's prompting.

Consistent quality comes from a consistent process — not from hoping each engineer prompts well. Define the workflow once: the steps the AI runs, the checkpoints where it stops, the reviews it must pass. Every session inherits the same standard.

Implement a Feature
Execute the engineering phase on a tracked work item — handoff, story breakdown, implementation waves, PR review, delivery.
"implement SHI-784"
# Step Ask to continue Skills Enabled
0
Fetch Work Itemfast
NeverAI decidesAlways
1
Story Breakdownbalanced
customized
NeverAI decidesAlways
2
Change Impact Analysiscapable
NeverAI decidesAlways
3
Technical Discoverycapable
customized
NeverAI decidesAlways
1
4
AI-Augmented PR Reviewcapable
NeverAI decidesAlways
2
5
Notify PM of Changesfast
NeverAI decidesAlways

Set the policy once — it runs the same way for every engineer, every session.

Ask to continue Per step: run silently (Never), let the AI decide when to ask, or Always pause for human approval.
Skills Require the local skills your team already uses in Claude Code, Codex & Cursor — your tooling becomes policy.
Enabled Turn any step on or off. Set once at the org level, fork it per team.
See all built-in workflows
Cost Control

Stop paying frontier prices
for routine work.

Every workflow step is tagged with the model tier it needs. Routine steps hand off to a cheaper model in an isolated sub-agent; the frontier model stays reserved for the work that's genuinely hard. Most tokens end up as cheap cache reads, not fresh frontier calls.

Token Intelligence — see what your team's AI actually costs, broken down by token, model, and tool, all in one place.

Token intelligence No integration required
Estimated cost · 7d
$115
across Claude & Codex, every model
Cache reuse
22.4×
context reused, not re-billed
Token composition 94% cheap cache reads
Fresh input1.1M <1%
Cache reads105M 94%
Cache writes4.7M 4%
Output732K <1%
By model — frontier where it's needed, pennies for the rest
claude-opus-4-887%$100
gpt-5.6-sol11%$12.42
claude-haiku-4-51%$1.39
gpt-5.6-luna<1%$0.02

Forge meters every token across the AI tools you already use — read from the usage Claude Code and Codex already record, with no proxy between your tools and the model.

Available with AI tools that support sub-agent delegation — Claude Code, Codex.

Visibility

See what AI is actually doing
across your team.

Is AI making your team faster? Where did the time go this sprint? Every AI action writes itself back to Jira, Linear, and Notion automatically — open the dashboard and the answer's already there, stage by stage. The same record answers the board question and the audit question.

Total AI time All AI-assisted activity Forge tracks across your tools — only SDLC work, not general AI usage.
1d 5h
▲ 21h 22m
Forge sessions
63
▲ 42
Workflow runs
40
▲ 26
Active users
4
▲ 1
Work items
12
▲ 4

Recent Activity

Planning Design Development Testing
Work Item Title Total Time Time by Stage Status Last Active
ENG-412
User onboarding flow redesign
test-driven-development
1h 25m
6211
Development Just now
Jun 10, 02:21 AM Planning 4m Fetch Work Item
Jun 10, 11:43 PM Other 2m Status Report
Jun 11, 10:12 PM Planning 3m Update Work Item
Jun 11, 10:16 PM Other <1m Resolve Work Item
Jun 11, 10:22 PM Design 15m Architecture Scan , Architecture Discussion
Jun 11, 10:34 PM Other <1m Session Feedback
Jun 11, 11:36 PM Planning 29m Update Work Item , Fetch Work Item , Readiness Check , Epic Story Breakdown , AC Quality Check , Story Review
Jun 12, 09:46 PM Other 4m Review Write Back , Notify PM of Changes
Jun 12, 09:50 PM Development 1m Check Branch Freshness
Jun 12, 09:54 PM Planning 3m Dependency Analysis
Jun 12, 10:00 PM Design 19m Change Impact Analysis , Technical Discovery , Define Test Strategy test-driven-development
Total1h 25m Planning41m Design34m Development1m Other7m
Contributor john.doe@acme.io
ENG-388
Self-serve billing & plan management
test-driven-development
26m
251
Planning 22h ago
ENG-401
Cross-tool token pricing
code-reviewsecurity-review
21m
4131
Review 23h ago
ENG-356
Refactor notification service
2m
111
1 day ago
ENG-339
API rate limiting & throttling
simplify
56m
1111
Review 2 days ago
ENG-318
Audit log export to CSV
review
14m
161
Review 6 days ago
For Teams

Set the workflow once.
Every role feels it.

Engineering Leaders

Finally see what AI actually shipped.

Show exactly what AI shipped last quarter, how long it took, and what it cost — drawn from the AI's own reported activity, not a monitoring tool bolted on top. Governance, compliance, and ROI in one trail.

Engineers & Tech Leads

Less prompting. Better first pass.

Forge briefs the AI with your architecture and standards up front — so you stop re-explaining your codebase every session, and the first pass holds up in review instead of bouncing back. It runs inside Claude Code, Codex, and Cursor, and the skills your team already wrote become the steps.

Product Managers

See where it stands — without the chase.

Every AI action writes itself back to Jira, Linear, or Notion. Open the work item and see what's done, stage by stage — no standup, no pinging engineers mid-build.

Finance & Operations

Forecast AI spend — don't discover it.

See cost by token, model, and tool across Claude and Codex in one place — so AI spend becomes a line you can plan around, not a surprise on the invoice.

Pricing

Start free.
Scale when it matters.

Free for individuals, forever. Add your team when you're ready — and Business when you need enterprise security and compliance.

Individual
Freeforever

Everything you need to ship with AI on your own — automated workflows, full audit history, and your favorite tool integrations.

What's included
Works with Claude Code, Codex & Cursor
Smart model routing
Industry best-practice workflows
Workflow configuration
Basic analytics
Business
Coming Soon

For organizations rolling out AI across all teams — with the security, compliance, and support that requires.

Everything in Team, plus
Unlimited members
Enterprise SSO
Enhanced roles & permissions
Priority support

Interested in early access? Talk to us →

Built with Forge

Forge was built by AI.
Governed by Forge.

We run the same governance on the AI that builds Forge: every workflow briefed, every SDLC stage tracked, every action logged.

Built with Claude Code · Codex · Cursor

Give your whole team
your best AI workflow.

The same workflow, cost control, and audit trail — across every engineer on your team, every session.

Start free → See pricing