What the workspace should look like when the agent can actually ship work
There are too many "another AI notes app" — Notion UI plus a chat box, branded as an AI workspace. Kition is trying to build something different.
The data is yours, not the cloud’s
A Kition document is a real .md file on disk. The vault is a folder. Any Markdown editor, Git client, Obsidian, or Vim can open it. If Kition the company disappears tomorrow, your work does not. We make exit a property of the architecture, not a promise.
The model is your call
OpenAI Responses, Anthropic Messages, AiApiy, DeepSeek, Qwen, Moonshot, self-hosted Ollama — all first-class. API keys stay local. Who you call, what you pay, which wire format you use — your decision.
The agent should really do things
A text-emitting LLM is not an agent. Kition ships a real tool surface: filesystem reads and writes, command execution, apply_patch, web fetch, a real Chromium browser, MCP servers, and subagent collaboration. It can do far more than chat.
Controllable, auditable, extensible
Hooks let you inject shell scripts at six lifecycle points — audit, comply, cache, transform. Subagents are bounded at depth ≤ 2 and ≤ 4 concurrent. Every tool call is visible and traceable.
A desktop app, not another browser tab
Electron plus a Go sidecar means Kition boots fast and stays responsive. File I/O, command execution, and browser sessions go through native APIs, not HTTP shims. Battery-friendly, offline-capable.
Ready when you are.
Kition is a local-first AI workspace. Markdown documents, structured tables, and an AI agent — running on your own machine, against the model provider you choose.