~~Remember to update the docs.~~

Push the code. The document comes with it.

Forge is one living document for people and their coding agents. Agents read it before they work and rewrite it as they code. When you push, the new chapter reaches your whole team, along with what changed and what was checked.

Download from GitHub See how it works

Free during beta. Windows and Mac. Works with Claude Code and Codex. No AI key and no credit card.

Claude Code · harbor-api

add a limit to checkout retries
forge_briefingCheckout: goal, 3 acceptance items, talks to Payments
reminderYou rejected retrying in the background. Customers were charged twice. (Mina)
editsrc/checkout/retry.ts
forge_save_changeschapter rewritten, 1 acceptance item changed
forge_record_checktest: 24 passed
commit and push
git pushmain → origin
forge_pusheddocument updated, team version 265

Harbor › Systems Team version 264 · Everything here is shared Team version 264 · Claude Code is working on Checkout Team version 265 · Everything here is shared

Checkout

Mina + Claude Code · just now

Goal

Take payment once, even when the network fails.

Owns

Cart totals, payment attempts, receipts

Doesn't own

Refunds, tax rules

Acceptance

One order can't be paid twice.
A failed payment can be retried.
A failed payment retries at most 3 times, then asks the customer.

Talks to

Payments, Inventory, Notifications

Checks

Reported pass 24 tests at 8c0792d
Not run Payment sandbox

Tom's computer took version 265 by itself.

Sample project. The tool names are the real ones an agent calls.

Goal

After a week of agent work, can you answer three questions?

What changed?

Each work item says what it will change, system by system: added, changed or removed, with the person and the agent who did it.

NotificationsNew system. Tom + Codex
CheckoutChapter rewritten, 1 acceptance item changed. Mina + Claude Code
Legacy exportRemoved, replaced by Reports. Mina + Claude Code

How does it work now?

Every system has one chapter with the same parts: its goal, what it owns, what it doesn't, how to tell it's done, and what it talks to. Agents rewrite the chapter along with the code. If the files change and the chapter doesn't, Forge says so.

Goal: Keep stock counts right across every store.
Owns: Stock levels, reservations
Doesn't own: Prices, supplier orders
Talks to: Checkout, Notifications

src/inventory/reserve.ts changed after this chapter was written at 8c0792d.

What still needs checking?

A pass is labelled as reported, because an agent said so. A result with a file attached says so. A test nobody ran says Not run. An unchecked system can't pass for a checked one.

Reported pass Checkout: 24 tests at 8c0792d
Result attached Search: load test report
Not run Payments: no sandbox account yet

Chapter

The loop runs through your normal push.

The agent reads
Before it touches code, your agent asks Forge which systems own the files, what they must do, and what was decided before.
The agent writes
As it codes, it rewrites the chapter, updates acceptance and records the tests it ran. This stays in a work item on your computer.
You push
Ask your agent to commit and push. Forge checks that the push reached the remote, puts the work into the document and shares it.
The team gets it
Parts only one side changed combine by themselves. If both sides changed the same part, the local text waits in a work item for an agent to combine.

Owns

Agents start every session blank. Forge hands them the project.

A briefing before the first edit

Give it a file or a task. It answers with the systems involved, their acceptance, and what else a change could touch.

forge_briefing

A memory of what you turned down

Decisions and rejected directions stay with each system. When new work looks like something you rejected, the agent gets your reason.

forge_record_decision

Test cases tied to acceptance

Agents keep test cases mapped to each acceptance item and see which ones went stale when acceptance changed.

forge_acceptance

Verification on request

Ask an agent to compare a system with its code and tests. When the system changes later, it goes back in the queue.

forge_verification_queue

Small reads

Summaries first, then one system or one paragraph at a time. The first read of a project with about 100 systems is around 30,000 characters.

forge_read

What the agent gets back after saving

rejected: Retrying in the background
why: Customers were charged twice.
by: Mina
matched: retry, background

The plan, flows, data model, tables and every past version live in the same document, and agents keep them current too.

Talks to

Everyone reads the same version, including people who never open a terminal.

Your team: Invite people by email as viewers or contributors. You can see who has the project open and which systems their agents are on. Two agents on one system get a notice, and nothing locks.
People who only read: Producers, designers and managers read the current document in the app without touching a terminal.
Your agents: Claude Code and Codex connect over MCP once per computer. Run several agents across several projects at once. Forge picks the project from the folder each agent works in.
Your code: Forge reads your Git repository on your computer to see commits and files. The document goes to the cloud. Your repository doesn't.

Working with you now

Mina + Claude Codein harbor-api · is working on Checkout
Tom + Codexin harbor-web · is working on Checkout
Annin the Forge app · reading Inventory

Mina + Claude Code and Tom + Codex are both working on Checkout.

Doesn't own

Left out on purpose.

Built-in AIYou keep your own agent and your own subscription. There's no AI key to set up.
An approval queuePeople click through approvals without reading. A push is the confirmation, and agents do the checking.
Anything that blocks youFailing checks and stale chapters warn. You decide what to do about them.
Public share linksReading a project takes an account and a place on its team.

Checks

The same labels, on Forge itself.

Forge 0.5.31 · 2 November 2026

Reported pass	In daily use by one game team: 103 systems and more than 260 shared versions.
Reported pass	More than 450 automated tests on Windows 11, including who can read and write what, by role.
Partial	The Mac app isn't registered with Apple yet, so you run `xattr -cr "/Applications/Forge Engine.app"` after installing it.

Acceptance

Done when your agent rewrites its first chapter.

Install Forge and create a project
Download it for Windows or Mac and sign in. A project only needs a name.
2
Open Forge for agents
Go to Settings, Agents, and press Turn on. The same page shows the exact line for Claude Code or Codex, with your computer's paths.
```
claude mcp add --scope user forge -- "the path Forge shows you"
```
Give your agent real work
When it's done, ask it to commit and push. Then open Forge and read the chapter it wrote.

Notes

Questions people ask first.

Is it free?: Yes, during the beta, with no credit card. If that ever changes, you'll hear well before it does.
Why does my computer warn me when I install it?: The installers aren't code-signed yet. On Windows, choose More info, then Run anyway. On a Mac, the app isn't registered with Apple yet, so drag it onto Applications and run xattr -cr "/Applications/Forge Engine.app" in Terminal.
Where does my data live?: Work in progress stays on your computer. The shared document is stored in Supabase, and only members of the project can read it. The privacy page lists everything.
How is the Mac version different?: There are installers for Apple silicon and Intel. They don't update themselves yet: Forge tells you when a new version is out, you drag it onto Applications, and you run the xattr command above again.
Which agents work with it?: Claude Code and Codex have setup steps in the app. The connection is MCP, so other MCP clients may work, but we haven't tested them.
Do I need Git?: No. A project can start as a name and a conversation with your agent, and you can link a folder later. Without a push, press Update document and share in Local work.
What if two people change the same system?: Forge combines the parts only one side changed. Parts both sides changed wait in a work item for an agent to combine, and the agent tells you what it did.
What happened to Forge v1?: Forge v1 has closed, and this site replaced it. v2 is a separate app with its own accounts and projects. If you need a copy of your v1 project, open an issue on GitHub and say you'd like us to contact you.

Try it on your next push.

Download from GitHub