I thought I loved OpenClaw, but I just loved Claude Code

First contact

There's a moment everyone who enters this world remembers clearly. It wasn't when I read the article, or when I watched the video. It was when I ran the first command and something responded. Something that reasoned. Something that built.

The first code agent I tried was Gemini CLI. The promise was simple: a language model that could read your code, understand what you wanted to do, and act. It impressed me. But it was like seeing the ocean from the shore without knowing how to swim.

Then OpenClaw appeared on my radar. A different interface, a different way of orchestrating agents, of giving personality to the tools. I dove in. And that's where the confusion started.

The Opus boom

There was a specific moment where everything changed scale. I plugged in the most capable model available — the most powerful, the most expensive — and what happened next I wasn't expecting.

It's not easy to describe that moment without sounding exaggerated. But it was like giving a jet engine to something that had been running with a car engine. The responses changed in depth. The decisions the agent made changed in quality. The conversation got dense.

And I made a decision I had never made until that day with any software tool: I paid $100 a month for the first time in my life for a subscription. It wasn't an expense. It was a signal I sent myself. This is worth it.

The floor that disappears

Then they put up the block.

OpenClaw could no longer connect to Claude. Overnight, the tool I had invested time, energy, and money in simply didn't work for the thing that mattered most. That feeling has a name: it's when you discover you built on sand without knowing it.

Epictetus wrote something that sounds simple until you live it: "Do not lament what you do not have. Rejoice in what has not yet been taken from you." In that moment I didn't remember it. I lamented. I uninstalled and reinstalled more times than I should have. I wanted it to work the way it used to. I wanted to recover what I thought was the love.

But it wasn't the love. It was the wrapper.

What I had actually learned

The process of breaking OpenClaw, reinstalling it, understanding why it failed, looking for alternatives — that whole cycle of frustration — taught me something I wouldn't have learned any other way: how the world of code agents works on the inside.

Not as a user. As someone who understands the architecture.

When I finally got to Claude Code directly — without intermediaries, without extra layers, without tools that wrap it — it was strange. It was simpler. More direct. And it worked exactly the way I wanted OpenClaw to work. Because Claude Code is what I was looking for. OpenClaw was a bridge to something I didn't know existed yet.

Ignorance led me to the bridge. The bridge led me to the destination. And the destination was the same from the start — I just didn't have the vocabulary to name it.

A world that doesn't wait

This world has a brutal characteristic: what you learn today is old by next week. Gemini CLI evolved. OpenClaw tried to keep up. Claude Code appeared. And while I'm writing this, there's something new I don't know about yet that in six months I'll use as if it had always existed.

Loyalty to a specific tool in this context is a trap. What lasts isn't the tool — it's the understanding you built using it. Every install, every error, every block, every restart: all of that became judgment. Capacity to evaluate. Speed to learn the next thing.

Marcus Aurelius would call it amor fati: loving not just what comes, but the clumsy path that brought you here. Including the mistakes. Especially the mistakes.