The Changelog: Software Development, Open Source
The Changelog: Software Development, Open Source
Changelog Media
From zero to NanoClaw (Interview)
2 hour 42 minutes Posted Oct 9, 2026 at 7:00 pm.
Changelog time!
Sponsor: Coder.com
Start the show!
From developer-manager to agent architect
The 40-hour weekend that launched NanoClaw
Giving away the crown jewels under MIT
Turning open source trust into a business
Building an enterprise agent factory
Skills, recipes, and maintainable forks
Sponsor: WorkOS
Agents at home and work
Context sharing and approval gates
The security onion
Designing the human-agent workflow
Keeping humans at the center
When agents become business-critical
Open source core, enterprise control plane
Keeping coding agents on the path
Contribute skills, not code
Sponsor: Buildkite
Remixing NanoClaw into new businesses
A partner ecosystem for vertical agents
Docker, Apple containers, and isolation
The many flavors of personal agents
The Linux of agents
SQLite, WAL, and Turso
Agent comments and Agent Flow
Durable context beyond chat
Wrapping up
Closing thoughts and stuff
0:00
2:42:51
Download MP3
Show notes
Gavriel Cohen, creator of NanoClaw and co-founder of NanoCo, joins Adam to explain how a 40-hour weekend project became a viral open source hit and the foundation of an enterprise AI company. Gavriel describes the security concerns that led him to build a small, container-isolated alternative to OpenClaw, why he released it under the MIT license, and why the project's community and credibility are more valuable than keeping its code private.
They explore the shift from writing code to architecting the environments in which agents work, NanoClaw's "skills over features" approach, the approval and governance layers required inside large companies, and a future where every worker manages agents without surrendering human judgment. They close with the technical simplicity behind NanoClaw, containers, TypeScript, SQLite, and a two-database design, and Adam's case for durable Agent Flow artifacts that keep organizational context from disappearing into chat.