July 22, 2026

KaKeKiKoKu Studio steps outside

No new feature to show today. The news is that the world can now find Studio.

For much longer than I ever planned, Studio has been built almost in silence. First because it was not ready; then because there was always one more version to ship, one more bug to fix, one more idea that could not wait. The result is a product in Beta, on Windows and Linux, that I use every day to build itself. I am not complaining about that part: building is what I enjoy most.

But a tool nobody knows about is half a tool. So today’s news is different from the usual kind: there is no new feature to show. The news is that Studio is starting to step out into the world.

The first step is already taken. Studio is, before anything else, an MCP citizen: the natural way it talks to your AI is the Model Context Protocol. And the MCP ecosystem has an official registry — the place where IDEs and directories look up which servers exist. Studio is now there. In practice it means something very simple: if your IDE supports the MCP registry, Studio is one click away, no configuration files involved. And underneath, nothing changes: what gets installed is just the key that opens the same free desktop app as always — 100% local, no accounts, no telemetry. The house is still the house; it simply has a doorbell on the street now.

More steps will follow this one, without rush: showing up in the ecosystem’s directories, in the lists where software gets compared and discovered. Little by little, like everything in Studio.

I will say it with the usual transparency: this is harder for me than programming. I have spent a year comfortable in my cave, building with an AI as copilot, and going out to show the work is a muscle I have never trained. But the product walks on its own now, and it deserves to be seen. If you arrived here from one of those new places: welcome. The best part is inside.