Stories, updates, and insights from building KaKeKiKoKu Studio.
The files are plain text. The engine that keeps them current, connected, bounded, and useful is doing far more than storing words.
Read the essay →
Studio 1.21 focuses on quality: repeatable checks, a useful report when something fails, and a tree that keeps your place. How the checks found real bugs, and what a successful result does and does not tell you.
Read the post
KaKeKiKoKu Studio 1.20: read connected knowledge in a consult area without leaving what you’re editing, see exactly what your AI receives when it opens a project, one word for each idea, an up-to-date Learning Lab and up to twenty relations in the same space.
Read the post
How I run versions with several AIs at once: rules born from mistakes, an architect AI and a builder AI, reviews by another company’s AI, three holes we found in my own process this week, and the question about the product they led to.
Read the post
KaKeKiKoKu Studio 1.19: when knowledge changes, your relations now show what needs a review. How a long conversation with Claude and ChatGPT, and one more doubt, led there. Plus format 1.1, more precise search, a refreshed look and an important fix.
Read the post
KaKeKiKoKu Studio 1.18: the navigation tree now shows your project’s knowledge, not only its files. Why the product no longer calls itself a memory layer, a new Extras menu with Blocks, and a fix for your AI.
Read the post
KaKeKiKoKu Studio 1.17: a common instruction file connects your local AI without MCP setup. The same projects, commands, and help, with a simpler first step.
Read the postA new identity, better readability and stability, more complete document reading, and an AI that can query the resource you are viewing. Plus two new ways to reorganise knowledge: convert reserved sections and integrate blocks into another section’s text.
Read the postA broader name for software built around meaningful blocks, with an open-ended roadmap for the file format, new integrations, new capabilities, and new kinds of products.
Read the postRun Studio inside ChatGPT (Codex) or Claude Desktop Code, where you and your AI can see the same knowledge workspace without leaving the conversation.
Read the postNo new feature today. Studio is now in the official MCP registry, and this is the start of showing up in the places where software gets discovered.
Read the postAbout a thousand changes, a quarter of the Studio Web app rebuilt, and a second-generation command language for AI — under an interface that still feels like Studio.
Read the postRelationships get budgets, prose gets more room, Studio learns to teach itself with the Learning Lab, and an open project now shows whether your AI can see it.
ReadRelationship arrows, project map mode, knowledge movement, quick file viewers, and full freedom to organize and connect knowledge from the navigation panel.
ReadStudio is now in Beta. The plan out loud — and why the next version will be a jump straight to 1.10.
ReadThe left panel becomes a real knowledge navigator, the local port can be selected, and Studio takes its first step out of Alpha and into Beta.
ReadA sync panel that hides when there is nothing to see, controls always within reach, and a calmer experience across windows.
ReadThe size caps in Studio are not technical limits. They are the design bet at the heart of the project — and the reason your AI thinks more clearly inside it.
ReadAn update focused on building a solid writing foundation with a new dual-mode Markdown assisted block editor.
ReadImportant images can now carry context, relations, and meaning instead of sitting silently in your project folders.
ReadThe promised Linux build is now available as an Early Access Snap Store Candidate.
ReadAn update centered on the editor and the small details that change a working day.
ReadTwo early releases after 1.0: one made Studio easier to live with, the other opened it beyond a single AI client.
ReadAfter a year of failed installers and long conversations with AIs, KaKeKiKoKu Studio 1.0 is finally downloadable.
ReadHow KaKeKiKoKu Studio was born from failure, stubbornness, and the certainty that something fundamental was missing.
Read