Kition

English · 简体中文 · Русский · 日本語 · Tiếng Việt · Français · Deutsch · Español

Documents, Tables, Whiteboards, Agents, and Workflows in one desktop workspace.
Write connected knowledge, think visually, build data tools, research the web, and automate repeatable work.

Download Kition

Website · Releases · Discussions · Contributing · Support · Security

Kition brings Markdown documents, structured table files, an infinite Whiteboard, a tool-using AI agent, web research, and visual workflows into one desktop workspace. Instead of making every task begin in a blank chat, Kition gives the Agent editable project files, typed records, attachments, and visible processes to work with. This makes powerful AI operations easier to inspect, correct, and repeat without handing context between disconnected tools.

Kition is currently in beta. Back up important workspaces and review agent changes before relying on them in production workflows.

Why Kition

• Connected documents. Write Markdown with live preview, links, backlinks, callouts, code, math, diagrams, daily notes, search, and export.
• Structured data beside the knowledge. Turn research and content into typed records, formulas, filters, groups, views, attachments, and AI fields.
• Visual thinking with reviewable AI changes. Build diagrams, mind maps, flows, and freeform sketches, then review Agent proposals before applying them to the Whiteboard.
• An Agent that can act. Search the web, inspect documents and table schemas, update content, and save useful output into the active project.
• Reviewable document edits. Let the Agent edit the active document, inspect every addition and deletion, then accept or reject individual changes.
• Visible automation. Assemble trigger-and-action workflows, test steps, inspect run history, and resolve missing inputs before enabling a process.

Let the Agent Edit—Keep the Final Say

Instead of returning another suggestion to copy and paste, the Kition Agent can read the active Markdown document, make scoped changes, and write the result back into the workspace. The document and the complete task trace remain visible together while the Agent works.

When a file changes outside the editor, Kition opens a document review surface that highlights additions, deletions, and rewrites. Each change can be accepted or rejected individually, or the complete edit can be reviewed as one set.

This creates a controlled document workflow: describe the goal in natural language, let the Agent edit the real file, inspect the diff, and decide exactly what remains in the final document.

Start With Work, Not a Blank Prompt

A capable Agent is useful, but a blank prompt still asks the user to design the task, describe every input, choose an output format, and recover when a step goes wrong. Kition moves that complexity into familiar work surfaces: documents, table fields, records, templates, and workflows.

The built-in scenarios below are ordinary .kitable files. Their prompts, field relationships, generated assets, and review states stay visible and can be adapted to a real project.

Generate campaign assets in batches

Start with a key message and a face photo. Typed fields keep the content type and intended emotion explicit, while AI fields generate linked 16:9 and 9:16 thumbnail variants for every record. The table becomes both the batch queue and the review surface.

Turn receipt images into searchable records

Drop receipt photos into an attachment field. Vision-powered fields extract the vendor, address, category, structured JSON, and plain OCR text directly into the same row. The results can then be filtered, corrected, summarized by the Agent, or passed into a review workflow.

Expand one product brief into a complete asset pipeline

One product concept can drive multiple design candidates, orthographic views, a feature image, a lifestyle shot, a style board, and launch copy. Each result remains attached to the source record, so the full chain is easier to compare, regenerate, and hand off than a collection of disconnected chat outputs.

Design posters from records, Boards, and the Agent

Design Studio turns a table record, a Board frame, or a generated image into an editable poster. Templates bind the workspace brand kit, size variants keep one composition across poster, story, square, and landscape, and the Agent proposes text and layout changes as a reviewable preview. Exports go back into documents and tables. See docs/design-studio.md.

These scenarios show the intended Kition loop: use documents for narrative context, tables for structured state, Whiteboards for visual thinking, the Agent for uncertain work, and Workflows for steps that should become repeatable.

Product Tour

Write connected documents Write Markdown with live preview, internal links, backlinks, tags, outlines, embeds, callouts, code, math, diagrams, templates, daily notes, tabs, and full-text search. Export finished work to PDF when it needs to leave the workspace.
	Turn data into useful tools Create structured table files with typed fields, attachments, formulas, filters, sorting, grouping, multiple views, and fast record editing. Use them for research, content pipelines, lightweight CRM, inventory, or project tracking.
Give the agent real context Ask the Kition agent to read and update documents, inspect table schemas, create or modify records, search the web, use tools, and follow a plan. Agent output can be written back into the active workspace.
	Think and plan visually Build diagrams, mind maps, flowcharts, sticky-note clusters, and freeform sketches on an infinite canvas. The Agent can inspect the board, propose typed changes, and let you accept or reject the preview before it becomes part of the workspace.
Automate repeatable work Build trigger-and-action workflows on a visual canvas. Start from a template, assemble a workflow manually, test individual steps, inspect run history, and resolve missing inputs before enabling it.

Also included:

• AI-assisted table fields for generating text, structured values, and media from record context.
• Email connections and inbox-to-table workflows. See Email Connections.
• Model, proxy, MCP, account, usage, update, and desktop integration settings.
• A seeded Getting Started workspace with practical document, table, and workflow examples.

Install

Desktop builds are published through GitHub Releases.

• macOS: download the latest .dmg.
• Windows: download the latest installer.
• Linux (experimental): download the latest x86_64 .AppImage.
• Previous versions: browse the complete release history.

Run From Source

Requirements:

• Node.js 22.19.0
• pnpm 10.33.0
• Rust (stable) and the Tauri system prerequisites for your platform

pnpm install --frozen-lockfile
pnpm dev

pnpm dev verifies and caches the pinned released runtime outside the Git worktree, then starts the Tauri desktop client.

For renderer, component, editor, and style work that does not require runtime integration:

pnpm dev:web

The web preview runs without the private runtime and is the fastest path for most client-side contributions. More options are documented in Runtime development.

Open Source Boundary

This repository contains the public React client and its Tauri desktop shell:

• document, table, Whiteboard, Agent, settings, email, scenario, and workflow UI;
• the Tauri desktop shell (src-tauri/) and desktop integration;
• public runtime contracts, mocks, fixtures, and black-box tests;
• packaging and unified release workflows.

The Kition runtime is maintained separately and its source is not included in this repository. Released desktop builds pair the public client with a signed runtime. Source checkouts communicate with it only through the public contracts in contracts/runtime/.

There is no Go source, Go module, or runtime source-build fallback in this repository.

Technology

Area	Stack
Desktop	Tauri 2 (Rust)
Interface	React, TypeScript, Vite
Documents	CodeMirror, Marked, Mermaid, KaTeX
Data and state	IndexedDB, Jotai, Zod
Testing	Vitest, Playwright

Contributing

Issues and pull requests for the public client are welcome.

1. Read CONTRIBUTING.md for setup, scope, and required checks.
2. Follow the Kition Development Standard, including the recommended Orca worktree workflow.
3. Keep changes inside the public client/runtime contract boundary.
4. Report security-sensitive issues through .github/SECURITY.md, not a public issue.

For product questions, account help, and private workspace concerns, see .github/SUPPORT.md.

Repository Layout

.
├── .github/                 # Community health files and CI workflows
├── contracts/runtime/       # Public runtime schemas
├── docs/                    # Product, contributor, design, and runtime docs
├── e2e/                     # Playwright black-box tests
├── public/                  # Static assets and onboarding files
├── scripts/                 # Repository checks and inspection entry points
├── src/                     # React application organized by feature domain
├── src-tauri/               # Tauri desktop shell, runtime manager, and packaging
├── tooling/                 # Build, lint, and test configuration
└── package.json             # Development, test, and packaging commands

License

Kition, including its runtime in crates/, is licensed under the Apache License 2.0.