Essays 5 min read

Agent Mode Feels Like the Iron Man Suit

The suit never replaced Tony Stark. It amplified him. That is the closest thing I have to a description of what it feels like to build software in agent mode, directing one or many agents and scaling your own thought and output.

Agent Mode Feels Like the Iron Man Suit

The thing about the Iron Man suit is that it never replaced Tony Stark. It amplified him. Without the man inside it the suit is an empty shell, and without the suit the man is just very smart in a cave. The whole point is the pairing. That is the closest thing I have to an honest description of what it feels like to build software in agent mode, and I have been chasing a better metaphor for months without finding one.

I dreamt of this, frankly, for a long time before it arrived. Not the specifics. The feeling. The sense that the distance between having an idea and having the thing could collapse, that a single person with enough clarity could reach further than a single person ever has. It is here now, and it has exceeded what I let myself expect.

What the suit actually amplifies

It is easy to assume the amplification is speed, that the suit just lets you type faster. That is the shallow version and it misses the real thing. The suit does not make you a faster typist. It makes your intent reach further. You decide where to go, and the machine handles the flying.

In practice that means I am no longer working at the level of the keystroke or even the function. I am working at the level of the task, and increasingly at the level of several tasks at once. I describe what I want built, the agent goes and builds it across the whole codebase, runs it, reads the failures, fixes them, and comes back. My attention sits where it is actually worth something: on what to build, on whether the result is right, on the decisions that compound.

The cost of producing the work dropped toward nothing. What is left is the part that was always the real job, and it turns out there is a lot of it.

Scaling thought, not just output

The part that still surprises me is what happens when it is not one agent but several. You stop being a person who does one thing at a time and start being something closer to a conductor. One agent is refactoring a module while another is drafting a migration while a third is checking a result. You are holding more in flight than a single human working alone could hold, and the holding is the skill.

This is where the suit metaphor strains in a good way, because it stops being about a single exosuit and becomes about commanding a small fleet. The bottleneck moves off your hands and onto your ability to keep several streams coherent in your head, to know which one needs you now, to catch the one that is confidently heading the wrong direction. It is genuinely a new way to think, not just a new way to type. You are scaling your own cognition, and the limit is how much intent you can keep clear at once.

Someone still has to fly it

I want to be careful here, because the suit is also exactly how you fly into a mountain.

It does what you point it at, fast, and confidently, and that is precisely the danger. A vague intent gets you a polished version of the wrong thing. A weak check lets a plausible mistake through at speed. The faster the suit, the more your judgment is the thing standing between you and a very efficient disaster. Power that does what you say is only as good as the clarity of what you say and the rigor of how you verify what came back.

So the discipline did not go away. It moved. I spend less effort making the thing and more effort being sure I asked for the right thing and that the thing is actually correct. That is not a downgrade. That is the work arriving at the place where a human is genuinely irreplaceable, and being freed to spend its whole attention there.

The most alive I have felt building

I am aware this can read as hype, so let me just say the plain version. This is the most exciting time of my life to be alive and making things. Not because the tools are impressive, though they are, but because of what they do to the gap between a person and what that person can build. The gap got small. A single builder with taste and judgment and a clear head can now reach the scale that used to require a team, and can keep the whole thing coherent because it is still one mind directing it.

The suit is real. It fits. And the strange, wonderful catch is that it makes the human inside it matter more, not less, because everything it cannot do, deciding what is worth building and knowing when it is right, is suddenly the only thing left to do.

If you want the method I run inside the suit, it is an AI agent workflow that holds up, and the book-length version is AgentSpek, free here. For how I keep the whole expanding system legible instead of overwhelming, that is the larger idea: coherent complexity.