July 19, 2026

KaKeKiKoKu Studio 1.15: the release you almost can’t see

About a thousand changes, a quarter of the Studio Web app rebuilt, and a second-generation command language — so Studio can keep looking like itself.

This release was supposed to be KaKeKiKoKu Studio 1.14.1. That tells most of the story.

The plan was modest: spend two or three days on one final review, finish the small bridge needed for the official MCP registry, publish the patch, and start showing Studio outside the quiet corner where I built it. I had already written the announcement before the release was ready.

Then I started reviewing.

I worked with the latest models from several AI companies, in their most demanding modes, and built a small mountain of prompts to examine Studio facet by facet: command language, state transitions, limits, structural operations, Web behavior, error messages, documentation, and the places where two individually reasonable rules meet.

Some passes found little. Some produced false positives. Enough of them found real problems.

The final review stopped being final, and the patch stopped being a patch.

The patch that became a rebuild

By my rough count, KaKeKiKoKu Studio 1.15 contains around one thousand individual changes. Roughly a quarter of the Studio Web app has been reconstructed. The command language Studio speaks with AI through MCP has been replaced by a complete second generation.

Most of this will be difficult to point at in a screenshot. There is no dramatic new screen, no new panel taking over the workspace, no feature designed to make the release notes look longer.

That is exactly the point. The visible Studio had already found its shape. This work was about making the structure underneath deserve that calm surface.

A new language for the AI

Studio has two users. You work through the Web interface. Your AI works through MCP.

The old command language had grown with the product. It carried decisions from a time when Studio itself was still taking shape: similar operations expressed in slightly different ways, names that could collide with language keywords, and small exceptions that made sense locally but no longer formed a clean whole.

In 1.15, that language has been reconsidered from first principles. Operations are small, typed and explicit. Project selection follows one consistent model. User-provided names are clearly data, not accidental grammar. The parser, executors, help, copyable errors and probes now share the same contract.

This is not a new version of MCP. It is the second generation of Studio’s own language over MCP: the vocabulary an AI uses to open projects, read knowledge, edit blocks, manage relations, search, move structure and reconcile context with reality.

For a human, this may be the least visible part of the release. For an AI, it changes the ground under every operation. There is less room to guess what Studio meant and more room to do exactly the right thing.

A quarter of the Studio Web app, without a redesign

The Web went through the same kind of work. About a quarter of it has been rebuilt, but I deliberately resisted turning that work into a new interface for its own sake.

I did not want existing users to relearn Studio. I wanted the flows they already know to agree with each other more often: fewer local exceptions, fewer actions that look equivalent but reach the engine differently, fewer strange moments at the boundaries between navigation, editing, relations, movement and synchronization.

The best result of this rebuild is not that the Web looks different. It is that it has fewer reasons to surprise you.

The question underneath the review

At some point I had to ask whether Studio had become too complex for the simple idea that started it.

I do not think it has. I think the problem was deeper than it first appeared. Keeping AI project context fresh is not the same as storing text. It means noticing change, preserving identity, maintaining a graph, enforcing useful boundaries, exposing the right knowledge progressively and protecting the line between what the project is and what its memory claims it is.

That deserves its own explanation, so I wrote it separately: KaKeKiKoKu Studio looks like text. It isn’t. It is the post I would give to anyone who sees the plain-text files and wonders why this needs an engine at all.

The version before opening the door

KaKeKiKoKu Studio 1.15 was not planned as a feature release. It exists because I wanted one last inspection before placing Studio in front of more people, and the product answered with more work than I expected.

The registry announcement could wait. It had been written too early. The first version a stranger meets should be this one, not the version I had before I started asking harder questions.

KaKeKiKoKu Studio 1.15 looks a great deal like KaKeKiKoKu Studio 1.14.

Underneath, it is not.

That is exactly the release I needed to make.