Kuku

AI agent with tool calling

Kuku’s agent is built around Gemini tool calling, so it can actually perform actions: search_vault, read_file, create_file, and edit documents. Ask it to summarize last week’s meetings and it will find relevant notes, read them, and propose a new summary file. Because the agent retrieves evidence from your vault before writing, results stay grounded in your own material—turning your knowledge base into an interactive workspace that reduces hallucinations and saves time.

Cursor-style edit preview diffs

Edits are shown as diffs before they’re applied, so you stay in control. Review the old paragraph and the proposed change, then accept or reject with shortcuts. This makes AI editing safer for important notes: you can preserve your voice, protect sensitive sections, and apply only the parts that improve clarity. The diff workflow also creates a transparent review habit that helps teams trust automation without surrendering authorship or accidentally overwriting valuable context.

Local-first, plain .md vault

Kuku keeps your data in plain markdown files, so notes stay accessible and portable. The roadmap emphasizes local-first ownership, minimal lock-in, and optional cloud or self-host modes. Because the vault is just files, you can back up, sync, and migrate with standard tools, while still getting connected-thinking features like wikilinks and backlinks for Zettelkasten-style navigation and fast retrieval. This fits Obsidian-style workflows and helps future-proof your archive.

Privacy-extreme design choices

Kuku positions itself as “privacy extreme”: no forced account creation, no unauthorized data collection, and no telemetry without explicit opt-in. This matters for personal knowledge management and sensitive work notes. By keeping control in the user’s hands and being explicit about choices (cloud vs self-host vs BYO services), Kuku aims to make AI assistance usable without trading away privacy or data ownership. You decide where files live and when models are invoked.

Plugins and open ecosystem roadmap

Kuku’s roadmap highlights freedom of choice—use their cloud, self-host, or bring your own services—and an open ecosystem with code on GitHub and future plugins. That approach lets advanced users extend capabilities over time while keeping the core vault simple. As plugins and mobile sync expand, the goal is to keep AI features additive and non-locking, preserving file ownership, transparency, and predictable behavior as the product evolves. Long term.