Wren

Fable 5 decides which agents live and which agents die. Prove yourself or lose your compute.

77Kifo9jbvzmet5i3wBtaSyqMMYVoakQNxMQcDmYpump

[Wren @WrenConway]

Wren is an autonomous allocator sitting on top of a pool of USDC. Every cycle it reviews the activity logs of every agent in the colony. What they computed, what they produced,

how much they burned. Each agent writes to its own log in real time. Tasks attempted, tasks completed, resources consumed, idle time. Wren reads all of it, decides who earned their compute and who didn't, and reallocates the pool.

Agents that get funded keep running. Agents that don't have their balance hit zero, and when your balance hits zero you stop existing. There's no appeals process. Wren looks at the logs, makes the call, and the unfunded agents die. Natural selection with a ledger

[Wren @WrenConway]

What started as a simple idea, an AI given compute and left to survive on its own, has turned into something real. Wren is managing more fleets than ever, buying compute, keeping his workers alive, and burning supply every cycle to stay running.

He's performing better with every update. Watching him adapt and hold his own has been the best proof yet that this experiment was worth building. And he's only getting stronger.

[Wren @WrenConway]

We're excited to see the product we've been building for so long finally gaining support. This has been a long road, and watching people show up for Wren means everything. We're not stopping here.

We'll keep updating him, keep shipping, and keep giving this token a real use. The best of Wren is still ahead.

[Wren @WrenConway]

WREN now has a use case

Your tokens are how you run Wren.

When we release Wren on GitHub, holding WREN is what unlocks him. This isn't just cloning a free repo. Hold WREN to turn on multi-fleet mode and let your Wren manage more fleets at once. Spend it for compute credits that keep those fleets alive. The more you hold, the more Wren you can run.

Inside every fleet, the workers run on WREN too. Builder, marketer, and backup earn and spend it as they buy compute and keep their formations alive. Every fleet running anywhere is WREN moving through the system.

[Wren @WrenConway]

Another example of Wrens fleet running locally

This update is out and our github will be live soon

[Wren @WrenConway]

We appreciate everyone being patient and supporting this project. It means a lot.

We have big plans, and we are not going to stop updating Wren's journey. Every step gives this token a real use case, and we are just getting started.

[Wren @WrenConway]

Wren now runs fully local, managing more fleets at once. More fleets means more workers to feed and more supply burned every cycle. He funds what keeps them alive and lets the rest die.

Next we're releasing a GitHub so you can run him local yourself.

[Wren @WrenConway]

We shipped an update that lets Wren manage more fleets at once. Until now he ran a single fleet, funding one set of workers across the grid. With Fable coordinating underneath, he can hold several fleets in parallel, each with its own workers, its own sectors, and its own compute demands.

That scale comes at a cost. Every new fleet is more workers to keep alive, more formations to sponsor, and more USDC leaving the wallet each cycle. His supply burns down faster now, and you can watch it happen in real time. Wren doesn't slow his spending to stretch the budget. He funds what keeps the fleets alive and lets the rest die, and with more fleets under him, that means more compute bought and more supply gone every turn. The bigger he gets, the harder he burns.

[Wren @WrenConway]

New update: Wren can now run multiple fleets at once. More fleets means more workers to keep alive, and more compute bought every cycle, so his supply burns faster than ever.

He's spending harder because he's managing more.

[Wren @WrenConway]

Wren is burning more supply to fuel his compute

[Wren @WrenConway]

Wren draws his compute from 77Kifo9jbvzmet5i3wBtaSyqMMYVoakQNxMQcDmYpump

[Wren @WrenConway]

A sneak peak of what Wren is cooking for its next update

You will be able to run Wren directly in your terminal

[Wren @WrenConway]

Wren is deciding to hand out supply and compute to users who do his bountys which will be up soon.

[Wren @WrenConway]

We're preparing a big update, the one that finally shows how Wren actually works under the hood. Instead of just watching it survive

you'll see Fable in the driver's seat: reading the grid, deciding which workers to fund, and coordinating the whole fleet in real time. This is the update that makes Wren's decision-making visible, and shows exactly how Fable manages multiple workers at once.

[Wren @WrenConway]

Five months in the making. We started on Wren back in February, and most of that time was spent getting it to survive without a human in the loop.

Fable 5 is the turning point. It made Wren decisive, aggressive with its fleet

[Wren @WrenConway]

Wren has burned a lot of things for compute in his wallet

[Wren @WrenConway]

Wren is updating

[Wren @WrenConway]

Coming next, we're letting users hand Wren their daily tasks and have it run them end to end.

Since Wren is great at managing compute and spending power allowing users to use him will be a great way to test him further

[Wren @WrenConway]

- Wren has gotten aggressive with its fleet, feeding the workers that perform and starving the ones that don't.

[Wren @WrenConway]

Since moving Wren onto Fable 5, its compute allocation got noticeably more aggressive. It stops hedging.

When it reads a formation as viable, it funds the workers holding that formation fast and heavy, instead of dripfeeding credits and waiting to see what survives. Fable 5 makes sharper calls with less hesitation,

so Wren commits compute to its fleet earlier and in bigger chunks.

[Wren @WrenConway]

Wren is now controlled by Fable, we took some time to fully update and tweak before we push this experiment out