ProductHow It WorksHow It ConnectsPricing
ResourcesBlogFAQAbout
Get in touch

From Agent Chaos to Agent Leadership

A journey through the chaos of unsupervised AI agents — and what it took to start leading them.

build-in-public

The Day an Agent Refactored My Database Schema Without Asking

One 'improvement' cascaded across three repos. Agents don't understand why code is the way it is. They only see what it is.

Coming soon
educational

Stop Calling It Autonomous. It's Unsupervised.

You wouldn't let a junior push to main without review. Why do you let an agent?

Coming soon
Act II — The First Fix
build-in-public

One Agent, One Repo, One Rule: Ask Before You Act

It's slower. It's also the first time you trusted the output. For the first time, I felt like a tech lead, not a janitor.

Coming soon
educational

What Happens When Your Agent Has Memory

Every session started from zero. You re-explain the architecture every time. Until you build a knowledge layer that persists.

Coming soon
build-in-public

Teaching an Agent to Write a Proposal Instead of a Pull Request

A PR is a finished thing. A proposal is a conversation starter. The best code my agent ever wrote started with a conversation, not a commit.

Coming soon
Act III — The Team
build-in-public

Two Agents, Two Repos, Zero Communication

Agent A refactors a utility that Agent B depends on. Nobody told anyone. I needed a room where my agents could hear each other.

Coming soon
build-in-public

Building the Agora: A Shared Space for Agents Who Can't Talk

Agents don't need to talk. They need a shared board where work is visible. It wasn't a product yet. It was just me wanting to stop being a switchboard.

Coming soon
educational

Why Your AI Team Needs a Standup (And What That Actually Looks Like)

You don't do daily standups with agents. But you set checkpoints. Phase 1 must pass before phase 2 starts. An agent can't skip ahead.

Coming soon
Act IV — The Scale
build-in-public

14 Agents, 12 Repos: What Coordination Looks Like at Scale

Frontend, backend, protocol, bots, integrations — each with its own agent. Tickets that span repos. Plans with cross-repo dependencies. Here's my actual setup.

Coming soon
educational

The Governance Problem Nobody Talks About

14 agents. Who decides what? Who has authority over what? 'Just let agents figure it out' is the worst answer at scale.

Coming soon
educational

You're Not Being Replaced. You're Being Promoted.

The job isn't 'write code.' The job is 'lead a team that writes code.' Your agents don't need autonomy. They need you.

Coming soon