Fractal Code
Hand it a plan and a team of coding agents builds the whole thing. One coordinator hands out the work, keeps the agents out of each other’s way and checks every change before it lands. It keeps going for days on its own.
You’ll join the Echofold newsletter, where Fractal invite codes will go out. Have a code already? Sign up with it.
Run a fleet of coding agents
Inside Fractal Code
Six agents, one control room.
A scripted replay of a normal day: the coordinator hands out work, answers what it can and swaps a finished worker for a fresh one, and nobody has to watch.
Work through the board. Refund jobs only run at night.
Check-in 25: s5 finished the calendar drag. I sent it for review and started a fresh s5 on lost messages.
Fix the double charge when a card payment is retried.
Found it: a retry charges the card twice. The fix is in, so I'm running the payment checks.
Cap how many alerts one outage can send.
Added a limit on incoming alerts. Running the checks now.
Link the old refunds that are missing their order.
214,000 refund records are missing a link.
Stop the sign-in test failing at random.
It waited a fixed two seconds. I've put a real wait in its place, and I'm scanning before I run it.
Coordinator: retry messages that fail to send.
A lost message was retried once, straight away. I'm making each retry wait longer.
Clear bookings that expired without being paid.
Expired bookings are now cleared every hour. Every check is clear, and I'm in line to add my work.
What it takes off you.
Less to watch, less to remember, less to decide. Everything it does for you, most important first.
01It works while you're away.
- Takes a build all the way to production on its own, running unattended for days or even weeks.
- Reduces your cognitive effort: it keeps track of every agent, task and decision, and only asks you when a call needs making.
- Answers routine questions, approves safe steps and swaps a finished worker for a fresh one.
- Starts from a plan built in Fractal Workflows, or from the tickets you already have.
- Leave it working while you're on the beach or out hiking.
02Your AI, your budget.
- Bring your own Claude Code or Codex subscription.
- Claude Code and Codex work side by side on the same job.
- Spreads the work across your subscriptions, based on the limits left on each.
- Shows what AI has cost you on every project.
- Open-source models, paid for as you go.Coming soon
03Nothing lands behind your back.
- Every change is tested and scanned for security holes, risky libraries and leaked passwords before it lands.
- Only new problems hold a change up, so years of old warnings never stall new work.
- Changes merge one at a time, each checked against the latest version, with a record of every check.
04Safe by default.
- Your agents run in the cloud on your own encrypted, always-on server, so nothing stops when your laptop does.
- Each agent works in its own copy of the code, so they never trip over each other.
- Passwords and keys live in Fractal Secrets, where the AI never sees them.
From a plan to production, on its own.
One real job, start to finish: online booking for a café's website.
You describe the goal, “let customers book a table online”, or start from a booking template. Fractal turns it into 14 tasks in the right order, and marks the 3 only you can do, like setting your opening hours.
Online booking14 tasks · 3 for you- Booking pageagent
- Time slotsagent
- Confirmation emailsagent
- Card depositsagent
- Set your opening hoursyou
- Choose the deposityou
- And 8 more, in the order they have to happen.
The coordinator gives each task to its own worker, with a private copy of the site, so no two can overwrite each other. Tasks that depend on others wait their turn, and yours are set aside for you.
Coordinatorhanding out the work- Booking pageworker 1
- Time slotsworker 2
- Confirmation emailsworker 3
- Card deposits, after time slotswaits
- Opening hoursyours
- Each worker gets its own copy of the site.
Workers build the booking page, the time slots and the confirmation emails side by side. The coordinator answers their routine questions, and when one finishes, a fresh worker starts on the next task.
Three workersbuilding side by side- Booking pagebuilding
- Time slotsbuilding
- Confirmation emailsfinished
- worker 215 or 30 minute slots?
- coordinator30, as the brief says.
- A fresh worker starts on card deposits.
Every change is tested and scanned for security holes before it counts. The card-payment key stays in Fractal's secrets manager, and the AI never sees it.
Time slotschecked before it counts- Tests48 of 48
- Security scannothing new
- Librariesno known flaws
- Keys left in the codenone
- The card-payment key is in Secrets. The AI never sees it.
Finished changes go live one at a time, each checked again against the latest version. In the morning, ask Rua what happened: booking is live, with a record of every step.
Liveone change at a time- Booking pagelive
- Time slotslive
- Confirmation emailslive
- Card depositslive
- RuaBooking is live. Fourteen tasks done, three of them yours.
On every change
Nothing lands unchecked.
Six agents or one, a small fix or a whole build: every change an agent makes goes through the same five steps before it reaches your main branch.
- 01
Its own copy
Each agent takes one task and works in a private copy of your code, so no two agents can overwrite each other.
- 02
Your tests
The change has to pass your project's own tests before it counts as finished.
- 03
Two security scans
One reads the code for security holes. The other checks your libraries for known flaws and looks for leaked passwords. Only new problems hold a change up.
- 04
One at a time
Changes go into main one by one, each checked again against the latest version, so two good changes can't break each other.
- 05
On the record
Every check and its result is kept with the change, so you can see afterwards exactly what was run.
Then it lands in mainEvery change · every agent · however big the job
Where it stands
Private beta, and what that means.
Worth knowing before you join the waitlist.
Private beta, by invite.
Fractal Code is open to private beta accounts. Join the waitlist and your invite code comes through the Echofold newsletter.
An always-on server of your own.
It runs on an encrypted cloud server that is yours alone, so it keeps going around the clock, whether your laptop is open or not.
It drives your AI tools.
Fractal Code isn't a model. It runs Claude Code and Codex on your own subscription. Open-source models are coming.
Get an invite to Fractal.
Fractal is invite-only for now. Join the waitlist and you’ll be added to the Echofold newsletter, where invite codes will go out to everyone.
Have a code? Sign up with it. Already in the beta? Sign in.