Notes from the eucalyptus
Why your assistant deserves a home, written while building it. From Kent C. Dodds.
Subscribe via RSSJuly 20, 2026
Your assistant's home
Your AI assistant accumulates things worth keeping. Memory, keys, code, scheduled jobs, an inbox. Those things should live somewhere durable that you own, no matter which agent you talk to this year.
July 20, 2026
Gateways connect. Homes accumulate.
MCP gateways and Kody get compared a lot, but they solve different problems. A gateway is a catalog of tools with pluggable ways to call them. Kody is a runtime where your assistant's stuff lives and keeps running. The difference shows up the moment you try to toggle code mode off.
July 20, 2026
The personal assistant that can't leak your keychain
My assistant's account holds 51 secrets. Here's the security architecture that makes the scary failure modes structurally impossible instead of policy-discouraged.
July 20, 2026
Why your assistant's home should make zero inference calls
Kody makes zero inference calls. That's not a limitation, it's the business model, and it changes who your assistant platform is actually working for.
July 20, 2026
Every install is a fork you own
In most ecosystems, installing someone's automation means renting a black box. In Kody's community, one-click install creates a fork you own. Here's why that changes how you treat other people's code.
July 20, 2026
The automations you never got around to building
Your real competitor for automation isn't a better tool, it's not automating at all. Why the activation energy of hosting and credentials killed your automations, and what changes when your agent has a durable home.
July 20, 2026
Self-service means ownership
Why Kody makes you create your own OAuth apps and bring your own keys, framed honestly. A few minutes of setup buy you your own app, your scopes, your rate limits, and no middleman between you and your data.