Start a run

Kind of run

Forge reads your brief, draws the sections and builds them.

Forge still plans, but keeps your lettered sections exactly and only assigns who builds each.

Both start with a 2-minute brief check. Nothing is built until you confirm it is you.

Add to what it is doing

It lands at the next step boundary, never mid-edit, and it carries straight on.

No file chosen yet

Test output


    
  

Logs

Download diagnostics

New project

Seven things, then confirm it is you.

Machine
What kind of thing it is
What it is written in

Nothing is deployed until you approve the first build.

The machine · 1 of 2

Add a machine

This asks for a production password. Forge uses it once, to install itself and leave a key behind. It is not stored, and nothing already on the machine is changed.

Used for this one install, then discarded. Never stored.

Nothing is touched until you confirm on the next screen.

Confirm & install · 2 of 2

Install on

About twenty seconds. Forge signs in as you, installs, then signs back in as itself to prove it works.

Machine
Signing in as
For
Set up repositories on it
Change how it deploys, from here

Paste it on

30:00 left on this link

1 · Download and read it

2 · Run it


Faster, and you run it without reading it first.

The link carries a public key. It is not a secret.

How deploys

On the machine —

What deployctl reads every time. Changing it needs your password and a code.

settings

On Forge — not on

Which code to build, how to gate it, which models to use.

backlog

Queue a build for

Forge checks the brief’s code rules now. The 2-minute brief check runs when you start it.

Test a commit on Forge's machine

Pick the branch Claude Code named. Forge's machine runs every suite on its last commit and, if they all pass, publishes the proof.

Remove this brief?

The brief is not kept anywhere else.

Audit this project

What will be published · 1 of 2

Put on GitHub

Read from .

Looking at what is on the machine…

Nothing is sent until the next screen.

Create the repository · 2 of 2

Create the repository

Used once, here, to create the repository and register the deploy keys — and not stored, exactly like a machine's admin password. Every git operation afterwards uses the deploy keys instead.

VisibilityPRIVATE
Who can readyou · 1 deploy key
That keyread-only

The Servers screen reads these back from GitHub afterwards, rather than repeating what was asked for.

In this order

1Write .gitignore
2Commit and push what is left
3Point the checkout at it with a read-only key

—

What it is

What is on it

Settings on this machine

What its projects need

Forge's agent

What you can do

Pounds per dollar for Activity figures

Activity's figures are Anthropic's list prices in US dollars. Forge shows them in pounds at this rate. It is a rate you choose, not a live one — Forge does not look it up.

Store a GitHub token

Forge checks it with GitHub before saving it, and shows you what GitHub says it is. It is used to create repositories and add deploy keys — every clone, fetch and push uses the deploy keys instead.

  • Can create repositories and add deploy keys for the owner above
  • Fine-grained, for the repositories Forge manages
  • With an expiry — Forge reminds you before it runs out
Make one on GitHub

Asks for your password. The token is never shown again.

Forget the GitHub token

Forge will ask for a token each time it needs one — publishing, connecting a repository, pointing a machine at one. Nothing breaks: deploy keys already registered keep working, because they are what git actually uses.

Choose a machine for

It gets a checkout of and a key that can only read it. Nothing is deployed yet.

Where the code goes

Leave it empty for that default.

An address on the machine that only a healthy new version answers.

Used once, to register the machine's read-only key, and not stored.

Finish setting up

Forge does these in order and stops at the first that fails. Pressing it again carries on from there.

    What already has on GitHub

    These files are already on GitHub and look like secrets to the scanner — usually test fixtures with fake keys, or the scanner's own rules. Approve them once, and a push is only stopped for a match that is not on this list, in a file the push changes.

    Remove

    This removes the key and its ssh alias from Forge. It does not remove it from GitHub — delete it there too if you want it gone for good.

    Replace 's deploy key

    Forge makes a new key beside the one in use and only switches to it once it has proved it can read and push. If any step fails, everything is put back and the current key carries on. The old key is not removed from GitHub — you decide that afterwards, separately.

      Remove the old key from GitHub?

      This is the key the replacement took over from. Nothing uses it now. Keeping it is harmless; removing it takes away this one key and no other.

      Replace 's key for

      makes a new read-only key beside the one it uses, Forge adds the new key to the repository, and the machine switches to it only after it has read the repository with the new key alone. If any step fails, everything is put back and the current key carries on. The old key is not removed from GitHub — you decide that afterwards, separately.

        Confirm the folder's new owner

        Remove the old key from GitHub?

        This is the key used before the replacement. Nothing uses it now. Keeping it is harmless; removing it takes away this one key and no other. The machine keeps its own copy for going back by hand.

        Save

        This changes what runs on , so it asks again even though you are signed in.

        Settings for

        Discard your changes?

        Upload a new version of Forge

        Choose the forge-vX.Y.Z-bN.bin file from the release. Forge unseals it, checks every file in it and gets it ready. Nothing is installed until you run one command on Forge's own machine.

        No file chosen yet

        Confirm

        Add a director

        They can do everything you can. What they approve is recorded under their name.

        At least 10 characters. Give it to them in person; Forge never shows it again.

        Their Claude account
        IDENTITY CHANGED

        changed its identity. Forge stopped.

        The machine answering on this hostname is not the one Forge saw last time. Nothing was installed and no password was sent.

        Which is it?

        You rebuilt or replaced it.

        Expected — a reinstalled machine has a new identity. Accept it below, then install again.

        You did not.

        Then something else is answering on that hostname. Leave it alone and find out what, before you do anything else.

        Remove ?

        This removes Forge's registration of the machine. It does not touch the machine.

        What stays exactly as it is

        What goes

        Add it back any time without re-enrolling: Forge keeps the machine's recorded identity, so re-attaching asks for no root password and installs nothing.

        Forge lets go of this project

        Delete

        What survives

          Held for 30 days

            What stops

              Key

              Replace release check token

                Asks for your password. The token is never shown again; a token with any write access is refused — Forge proves GitHub refuses a harmless test change to the repository, its settings, secrets and variables.

                A key Forge does not know

                It is not one of Forge's keys and no machine of yours uses it. If you do not recognise it, removing it is safest.

                Not sure? Close this — nothing changes.

                Remove this key from GitHub?

                Replace the key

                    Replace all Forge keys

                    Each project's write key is replaced in turn — the new one added and proved before the old one is removed. It stops at the first that fails and says what is done and what is left.

                      Lock down

                      For an emergency: Forge removes every one of its write keys from GitHub, stops the runs that are going, and forgets the account token. Servers keep pulling with their read-only keys, so production keeps running.

                      Removed from GitHub

                      Keeps running