forge.suqya.co.uk
Full review Two independent reviewers — the reviewer and the security auditor — read everything the branch adds. Never the shorter quick review. If a check fails, the fixer may bump the version and add tests, but never touches this project's rules files.
Claude's proposal
It lands at the next step boundary, never mid-edit, and it carries straight on.
Seven things, then confirm it is you.
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.
Where the code goes
What Forge will do, in order
About twenty seconds. Forge signs in as you, installs, then signs back in as itself to prove it works.
1 · Download and read it
2 · Run it
On the machine —
On Forge — not on
The brief is not kept anywhere else.
Read from .
In this order
What it is
What is on it
Settings on this machine
What its projects need
Forge's agent
What you can do
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.
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.
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.
It gets a checkout of and a key that can only read it. Nothing is deployed yet.
Where the code goes
Forge does these in order and stops at the first that fails. Pressing it again carries on from there.
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.
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.
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.
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.
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.
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.
This changes what runs on , so it asks again even though you are signed in.
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.
They can do everything you can. What they approve is recorded under their name.
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?
This removes Forge's registration of the machine. It does not touch the machine.
What stays exactly as it is
What goes
What survives
Held for 30 days
What stops
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.
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.
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