From zero to NanoClaw (Changelog Interviews #686)

What's up friends, welcome back. This is the changelog. What if the most important, valuable thing you own, your crown jewels, was code you just gave away for free the same weekend that you wrote it? Well, this week I'm talking to Gabrielle Cohen, the creator of Nanoclaw, about exactly that bet. We discuss why restrictive open source licenses are pointless in a world where agents can rewrite any code base in 12 languages overnight. how he sat down with a cloud code that didn't even know OpenClaw existed and built NanoClaw from a blank slate, the moment Karpathy tweeted and shut down a marketing agency doing hundreds of thousands in ARR, and Gavriel's vision for a human-centered future where every knowledge worker becomes a manager of hundreds of agents. Heads up, I'm doing a live show with Taylor Otwell at Resend Forward. Check it out at resend.com forward. And I hope to see you there. A massive thank you to our friends and our partners at Fly.io. That is the home of changelog.com. Your agents need a computer, and that is what they built. Learn more at fly.io. Okay, let's do this. Well, friends, this episode is brought to you by our friends at Coder.com, secure environments where developers and agents work in parallel. And I'm joined by Nicky Pike, field CTO for Coder. Nicky, what is a field CTO?

So I get that question a lot and it's, you know, half the people understand it, half the people don't. So a field CTO, I describe it very simply as we're dev rel for the C-suite. we provide a bridge between the customer voice between the c-suite and the managers and the leadership teams of our customers back into our product and then we go through and we help enable our teams to to have the same message to make sure that the message is correct and that we're building on something that people actually want not just something that we think they want

okay so we're taking the laptop away from the developer not really though we're putting them in a cloud development environment a secure environment where they can work with their agents in parallel these are blessed environments what's wrong with the laptop

The laptop is the trap here. And not only because the fact that it could be stolen, you could lose it, it breaks and you're out of work while you're waiting for a new one. But there's also just the consistency that you got

there.

We all know developers. Developers are going to be looking for some of the latest and greatest. And if you're not really controlling how they get out

there,

that's where you get this. It works on my machine. It doesn't work in production. It doesn't work anywhere else because you don't have that consistency. You don't have that ability to really standardize what that environment looks like. And this is a problem not only for new people coming in, you know, the onboarding statement is average, I think, is like four to five weeks for a new employee to really get their local laptop set up and ready to start doing their first time of code. And, you know, the time to first commit is a metric that almost everybody knows. And the reason they can't do that is because there's a lot of tribal knowledge out there. They got to go talk to other