One context, every way you write
A rule you keep on the desktop is in force on the command line and in your agent's session, and a check reads the same rule wherever it runs.
The context graph
The rules your project writes by: its terms, its voice, the decisions people kept, and where each one applies. kapi builds it from your files and keeps it beside them.
Context →Kapi Desktop
Open a folder. The Map shows your files, the rules in force and what an assistant noticed. Decide what becomes a rule, then open a file and fix a finding in place.
Kapi Desktop →Command line and agents
The same context in a terminal, in CI and in your AI agent: kapi writes the rules into AGENTS.md and CLAUDE.md, serves them over MCP, and fails kapi check on a failing finding.
Use with your agent →Languages when you need them
Add a target language to the project. kapi up translates what changed, reuses what was approved before, and holds back what needs a person.
Add languages →neokapi, the engine underneath
A content engine in Go. kapi is built on it, and your own programs can be too.
Formats
Readers and writers for documents, data and office files into one content model. An edit goes back into the file with its structure intact.
Formats →Tools and flows
Composable tools for checking, editing and translating content, run through streaming flows. Headless, from a terminal, an agent or your own Go program.
Go quickstart →Measured
Format support is measured. The format-maturity and benchmark dashboards show how each format holds up.
Dashboards →