· KaKeKiKoKu Studio 1.17.0
One file to get started
The first step should be trying the product, not working out how to connect it.
There was a barrier before anyone could discover what KaKeKiKoKu Studio is for: connecting it to their AI.
MCP works. I use it, and it is staying. But each client has its own settings, screens, and way of registering a server. For someone who just wants to try a tool, that is work before getting started. If the first step means stopping to figure out the connection, many people never reach the second.
I wanted that first step to be much simpler.
Open the application. Add the instructions.
This release offers another way in. Open KaKeKiKoKu Studio and add an instruction file to your workspace. It might be called AGENTS.md, CLAUDE.md, or whatever your editor expects. The content is the same: it tells the AI how to connect to Studio, already running on your computer.
There is no new plugin to install and no MCP settings to find. With the applications already installed, adding those instructions can take a minute. Then start a new conversation and check that your AI can see the projects you have made available.
It is one common guide. I do not want to replace eight different configurations with eight new guides saying almost the same thing. The part that depends on the editor is where it reads its instructions. The rest is shared.
The same knowledge, a simpler connection
Underneath, it is a local HTTP connection. You do not need to learn its protocol: the file explains it to the AI. Your AI needs tools that can make requests on your computer, with its client’s usual permissions. A remote chat without local access does not gain that capability just by receiving an instruction file.
The knowledge stays where it is. These are still your projects, your Wuniq files, the same commands, and the same help. Use MCP when it suits you. Where the client supports them, MCP keeps its application launch and channel notifications. In the new mode, you open Studio first and work in Precise mode.
That seems a reasonable condition to me: open the application you are going to use. KaKeKiKoKu Studio is also there for you to read, review, and edit the knowledge, whether or not an AI is working at that moment.
This change matters because of what it removes from the way. I want you to try what preserving your project’s decisions and context can do. Configuration should not be the part you remember most.
The Quick Start and the new common connection guide explain the route and provide the instruction files. Start there. If MCP is already configured and working for you, you can keep using it as before.