Gå til hovedinnhold

Kapi CLI or Kapi Desktop?

Both run the same engine on the same .kapi projects, flows, and tools — a workflow you build in one runs in the other, and you can switch any time. The only question is how you like to work.

Kapi CLI — the command-line tool​

A single binary that operates directly on your files. Reach for it when you want to:

  • automate — scripts, make targets, CI gates that fail a PR on a bad check;
  • stay in the terminal — flags, pipes, --json output you can feed to other tools;
  • work offline or at scale — batch a whole directory, no server, no GUI;
  • drive it from your AI assistant — over MCP or the Agent Skills, Claude calls kapi to read, check, and fix your content.

Start with the Kapi CLI recipes.

Kapi Desktop — the visual app​

A native app that wraps the same tools and flows in a visual interface — no YAML, no flags. Reach for it when you want to:

  • build flows on a canvas — drag tools, configure them in a form, run them live;
  • see your project — content collections, matched files, detected formats, and content memory laid out visually;
  • install plugins and store credentials through a UI rather than the keychain and config files.

Start with the Kapi Desktop overview.

Which should I pick?​

If you…Reach for
live in a terminal and want to script or gate thingsKapi CLI
are vibe-coding with Claude and want it to translate for youKapi CLI over MCP — Claude drives it
prefer clicking to typing, and want to see the flowKapi Desktop
are setting up a repo's languages and gates once, to commit and shareKapi CLI (your first project)
are reviewing translations and browsing memory and terms day to dayKapi Desktop

You don't have to choose permanently. The kapi.yaml recipe a teammate authors in the CLI opens in Desktop, and vice versa — same project, same results.

Next​