rulocode
Start free
Start free
Blog

Claude Fable 5.1 Build Day in Bogotá: we filled a room to see how far it would go

September 17, 2026· 4 min read
Claude Fable 5.1 shipped a little while ago, and last night in Bogotá we filled a room to see how far it goes. This was the Fable 5.1 Build Day on September 16, 2026: one night, a brand-new model, and a room full of people with their laptops open.
A room full of builders with open laptops during the Fable 5.1 Build Day in Bogotá
Every attendee got API credits. That changes the whole tone of an event: nobody is doing budget math before trying a dumb idea, and dumb ideas are exactly the ones that sometimes work. Teams came together right there. You could go solo or join two, three, four people you'd met minutes earlier. I showed up without a team and left with one.
TODO(rulo): name the hosts and the venue, and introduce your team if they want the credit.
The brief on screen was blunt: build whatever you want, as long as it pushes Fable 5.1. Then, the three tracks:
TrackWhat it meant
DelightSomething delightful
BreakthroughSomething you couldn't build before
EverydaySomething that solves a real problem in your day
The brilliant part is the fine print on the slide: the tracks describe the quality of what you build, never the topic. They don't tell you what to make. They tell you what you'll be measured against. That's the difference between a brief and a standard.
The hosts in front of the slide with the three tracks: Delight, Breakthrough and Everyday
After planning came the clock on the projector. I caught the timer at 28:59, and that number says more than any description of the event: there was no time for pretty architecture. There was time to decide, cut scope, and ship. And that's when the thing I wasn't expecting happened. From that point on it wasn't about the model anymore. It was the atmosphere in the room. Teams that had met that same afternoon building incredible ideas, all in record time. People standing behind someone else's shoulder watching a demo come alive. That hum a room gets when everybody is making something at the same time. A new model is an excuse. What actually produces things is a room full of people who want to build and a deadline that's an hour away. Everybody, literally. Demos on the projector, questions on the mic, a countdown on screen.
One of the demos projected at the front of the room
The peak of the night was a shout from the crowd — "¡Auto manual!" — and the whole room breaking into applause. I can't explain the joke without the context of that demo, and that's fine: some things only land if you were there.
TODO(rulo): tell us what your team built, which track you picked, and which demo stole the night.
Three things:
  • Credits are the unlock. When the API bill isn't yours, you try the weird idea. And the weird idea is the demo people remember.
  • A standard beats a topic. "Something you couldn't build before" forces you to ask what actually changed with the new model, instead of rebuilding the same CRUD against a different API.
  • The talent in Bogotá is ready and waiting for the excuse. All it took was a room, a projector, and one night.
Big thanks to the Anthropic community for opening up spaces like this in the city. So tell me: what would you build with a model that just shipped?
Newsletter

One real automation, explained, every two weeks.

What I'm building with AI for my work and my students': the flow, the click-based tools and the hours it gives back. No news digests.
No spam. Unsubscribe in one click. If you're already in Week 0, you already get it.
Rulo, the rulocode robot, at the final station of his world