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.
Documents, tables, research, and automation share context
Kition connects writing, structured records, browser research, Agent sessions, and workflows in one project surface. The agent can move between them without making you rebuild context in separate apps.
The model is your call
Choose Kition Cloud, OpenAI Responses, Anthropic Messages, the DeepSeek or Kimi preset, or a custom endpoint that implements a supported Agent wire. Sync the current provider catalog instead of relying on old model lists.
The agent should really do things
A text-emitting LLM is not an agent. Kition can expose document, filesystem, table, web, browser-context, image, artifact, and shell tools, with the available set reported by the runtime for each turn.
Controllable, auditable, extensible
Tool calls, plans, errors, artifacts, and changed files stay visible. Shell commands can pause for approval and supported table plans can require Apply. Public Hooks, MCP, Subagent, and universal permission setup are not exposed in 0.1.41.
A desktop app, not another browser tab
Electron plus a Go sidecar gives Kition native file access, command execution, browser sessions, and responsive desktop interaction without turning the workspace into another browser tab.
Ready when you are.
Kition is a desktop AI workspace for connected documents, structured tables, editable designs, whiteboards, visual workflows, and reviewable AI agents.