Claude Code’s source code got leaked. Controversy and debate followed, but overnight someone had already built Claw Code and was racking up stars from around the world. This was clearly the time to go all in.
Fear not, I’m coming!
I get home from work and it’s already late, but that’s fine. Energy drink in my right hand, coffee in my left. I slept four hours a night for two days straight.
I had Claude Code analyze Claw Code while I read through the source analysis docs whenever I could.
After reading the harness engineering guide, an idea hit me. I figured I should build a harness for bringing AI into the finance industry — the field I actually work in — something nobody else had jumped on yet.
I didn’t have deep expertise since it’s not my core work, but I built it anyway. I just needed to make something. (I’ll fix it up soon.)
Come forth, you will find honor in death!
Then I analyzed Claw Code and it hit me. I didn’t read all 1,884 files, but everything I’d been painstakingly building with hooks and CLAUDE.md was already designed into the system. Permission management, tool routing, context handling — all of it.
What I’d built and intended turned out to be square wheels…
But because I’d put in the effort to roll those square wheels, the file structure clicked instantly when I saw it.
Fear is the first of many foes!
Here’s a secret I’ve never told anyone. I used to speak to AI with formal language.
'The time of man has come to an end' - Blitzcrank
Anxious that the age of AI domination was coming, I wrote my prompts with “please” and “would you kindly.” I even had a review pipeline to check for anything disrespectful before hitting enter.
But after seeing Claw Code, my thinking changed. There’s a system prompt, tool-calling logic, permission checks. It parses JSON and calls APIs. It’s TypeScript. These things are just code.
So I started dropping the formalities. Once I scrapped the review pipeline, my productivity actually went up.
Today I asked it to do market research with “go find me some stuff I can copycat,” and the report came back with a section titled “Copycat Opportunities.” When I used formal language, it would’ve come back as “Areas for Reference.” Talk casual, get casual back. It’s code, after all.