July 2, 2026

KaKeKiKoKu Studio 1.12.0: the connected workspace

The release where relationships stop being hidden, the project map becomes visible, and now you organize and connect knowledge with full freedom: from wherever you want, including the navigation panel itself.

The last post said the next published version would be 1.10.1. In the end, it is 1.12.0.

The reason is simple: the stretch that was going to close KaKeKiKoKu Studio 1.10 grew. Not in a different direction, but further in the same one. First I wanted relationships to be visible. Then I wanted them to be created. Then moved and corrected. And when I used it for real, it became clear that this needed something else: a better way to look at the whole project, and a more comfortable way to open the real files behind the knowledge.

So this is not a small weekly release. It is a jump.

Relationships now have a visual presence. Studio can draw arrows between the resource you are reading and the resources, sections, or subsections in the tree. You no longer have to imagine where a relationship points: you see it. And from those same arrows you can create, select, move endpoints, or delete relationships.

And a missing freedom arrives. The left panel stops being only a place to look and navigate: you can now move sections and subsections and create relationships directly from it — even between two items in the tree — without always having to go through the central editor. And when you do, the selection follows the result: the central editor shows what you just moved or connected, so the action is never invisible. The only limit is the same as always: a resource cannot be related to itself.

That same panel can also become a project map: a wider, read-only view where resources, sections, descriptions, previews, and relationships appear together. It is the kind of view you use before asking the AI for something serious: first you look at the terrain, then you decide what to change.

There is also a quieter but important part: Studio now gets closer to the real files of the project. You can create a Markdown file with its Studio context from the left panel. You can edit Markdown and text directly. You can open source code in read-only mode. And you can inspect Word, PDF, and OpenDocument files as extracted text when you only need to read or copy their content quickly. Search fits the same idea: a result now shows where the match lives — in a resource's context or in the file itself — and a click takes you straight there.

Another improvement is less visible, but it matters: the AI receives better instructions for working with Studio, including the unpleasant case where a context file is damaged. The idea is not that the user has to understand the internal format. The idea is that Studio and the AI can recover useful knowledge without making the problem worse.

This is not the end of the road. Quite the opposite. This is where Studio starts to look like the tool I was hoping it could become: exciting, powerful, and finally delivering the functions it was meant to deliver. It is no longer only a place to store context. It is a space where you can see, connect, move, and verify the knowledge of a project.