Developers: keep "the state of my project" in the vault — let the agent iterate with you
The Kition agent runs exec_command and apply_patch and reads the design notes you wrote about why. That gives you a colleague who actually understands your architectural decisions — not just your current diff.
Not just an IDE copilot — a project memory manager.
Who it is for
Indie devs, SaaS side projects, CLI maintainers, OSS authors. No team — but lots of long-term context.
What hurts today
The IDE copilot sees code, not the Notion doc from three months ago explaining "why we ditched Redis for PostgreSQL." So the same decisions get re-made every quarter.
How Kition helps
Kition gives the agent code, source notes, ADRs, and the ability to run shell commands or apply patches. It remembers your history — you stop re-explaining the same things.
Suggested workflow
Step 1
Decision log → Markdown
One ADR.md per architecture call. The agent reads them on every subsequent prompt.
Step 2
Code + docs together
git checkout the project next to the vault. fs_grep and fs_read see both.
Step 3
Task table
Track issues, PRs, ideas in a data table. The agent can add_records.
Step 4
Ops & scripts
exec_command runs tests, curl, grep; apply_patch edits code. Hooks block anything risky.
Outcomes
- Agent gains long-term project memory
- Hooks make agent actions auditable
- One app replaces IDE-copilot, docs, and task board
- Fully local — great for OSS maintainers
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.