May 4, 2026

KaKeKiKoKu Studio 1.1 and 1.2: quieter, wider, more usable

Two early releases after 1.0: one made Studio easier to live with, the other opened it beyond a single AI client.

Not long ago, KaKeKiKoKu Studio 1.0 arrived on the Microsoft Store.

After a year of building, redesigning the core more times than I want to admit, fighting installers, and testing everything on real projects, version 1.0 was the moment to say: it exists. It can be downloaded. It can be used.

But publishing a first version is not the end of anything. It is when the product starts looking back at you.

KaKeKiKoKu Studio 1.1 and 1.2 are the first answers to that real use.

1.1: less friction, better daily flow

KaKeKiKoKu Studio 1.1 was a cleanup and flow release. It fixed bugs, polished editing details, and added something small on paper but very important in daily work: quick filters for Important, Pending, and Draft resources.

Studio preserves structured knowledge beside your projects, but preserving knowledge is not enough. You also need to return to what needs attention without digging through everything.

Important resources are the ones you do not want to lose sight of. Pending resources still need documentation, review, or closure. Draft resources are knowledge in motion: ideas not quite mature yet, notes that capture an intuition before it disappears, pieces still searching for their shape.

Those three filters made Studio feel less like a place where context is stored and more like a living work surface. You can see what needs care. You can see what is unfinished. You can see what should not be forgotten.

There were also quieter fixes, the kind that rarely look exciting in a release note but matter when you use the tool every day. For example, editing text inline should not fight with drag-and-drop. It sounds minor until it interrupts your thinking. Studio exists to reduce friction between you, your project, and your AI, not to add a new negotiation with the interface.

1.2: opening the core

KaKeKiKoKu Studio 1.2 moves in a different direction, and for me it is just as important.

Studio was born very close to Claude Code. That made sense: Claude Code was the first workflow where everything clicked, especially thanks to channels, which allow Studio to send events to the AI automatically.

But Studio was never meant to become subordinate to one provider.

Version 1.2 opens the core.

Studio still works beautifully with Claude Code, and that remains the deepest automatic experience today. But the product, the documentation, and the quickstart now reflect a broader reality: Studio is MCP-first. It can work with Codex, Antigravity, Claude Desktop, and other MCP clients through Precise mode.

Precise mode is not just a technical fallback. It is a legitimate way of working. Studio detects, organizes, and prepares the action; the user decides when to bring it to the AI. Less automatic magic, more human control.

That matters to me. Studio should help the AI become a better companion in the project, but it should not erase the human from the loop. The product proposes; the user decides.

1.2 also reorganizes the website and documentation around this idea. Studio is not "a tool for Claude Code." It is a local Knowledge Engine for working with AI, whichever client you use, as long as it can speak MCP.

What these releases mean

These are not fireworks releases. They do not try to look bigger than they are.

But they matter.

KaKeKiKoKu Studio 1.1 made the tool more comfortable to live inside.

KaKeKiKoKu Studio 1.2 made it more open outside a single bubble.

After 1.0, that was exactly the right work: listen, clean, open, and keep building without betraying the original idea.

Next: Linux

The next planned step is KaKeKiKoKu Studio 1.3 on Linux.

For me it is a natural move. Studio is local. It lives beside projects. It speaks MCP. It should not be tied forever to Windows. The Microsoft Store was the first place where I could make it downloadable and orderly; Linux is the next place where the idea needs to prove it can move.

After that, there will be more. Some ideas are already taking shape, and others are still in that dangerous zone where something looks brilliant until you try to implement it. I would rather not turn the future into a list of promises.

For now, this is enough: Studio no longer only exists. It is beginning to find its shape.