Gå til hovedinnhold

Kapi Desktop

Kapi Desktop is the visual companion for the kapi CLI. It provides a native desktop interface for building content flows, running tools, managing plugins, and storing AI credentials — all without writing YAML or remembering CLI flags.

Like the CLI, the desktop is project-first: it opens to your projects and reopens the ones you had last time, so a .kapi project — its languages, content, flows, content memory, and terms store — is the home you work from. One-off file runs still live a click away as quick tools (the ad-hoc mode), for when you just want to push a single file through a tool without setting up a project.

A guided tour walks each surface in motion — creating and managing a project, its content and flows, settings and providers, the terminology and content-memory explorer, and the plugin manager. The kapi CLI recipes note, task by task, how each maps to Kapi Desktop.

Features​

  • Project dashboard — Open to your projects and pick up where you left off. Each project home shows its languages, content collections, and each locale's standing against its ship gate, with Bring up to date a click away — and Plan… beside it, a pre-flight dialog showing the pending work, content-memory leverage, and a token estimate before anything runs (the desktop form of kapi up --plan).
  • Review surface — Work the queue of translations awaiting a person: inspect source and target with findings, edit, then approve, reject, or sign off — keyboard-first, with an optional AI pre-review to triage the queue. See Review & approve.
  • Flow editor — Build multi-tool pipelines visually. Chain AI translation, quality checks, pseudo-translation, and more into reusable flows saved in the project.
  • Flow runner — Execute a project's flows with live progress visualization: per-file status, node highlighting, and timing. Runs use the recipe's languages and content, so there are no flags to repeat.
  • Quick tools (ad-hoc) — For one-offs, run an individual tool or flow on a loose file with dynamic configuration forms generated from tool schemas — no project required.
  • Plugin manager — Browse the plugin registry, install, update, and manage plugins from a UI.
  • Connect your AI — On first open, a card offers the AI it detects — a Claude Code sign-in (uses your Claude subscription), a local Ollama model — one click; API keys go in the credential vault, stored in your OS keychain.
  • Project files — The kapi.yaml recipe is a portable file you can share via git; the desktop opens a project by its folder.

Install​

On macOS, the cask installs the app and bundles the kapi CLI:

brew install --cask neokapi/tap/kapi

For the Windows installer and the macOS DMG / Linux tarball builds, see Installation.

Your first project​

Your first project walks the create → add content → bring up to date → review path step by step; the guided tour shows each surface in motion. The shape of the work here: the project home is one surface — content collections plus each locale's standing against its ship gate — Bring up to date runs the default flow until every gated scope ships or parks, and the Review queue takes what parked. Provider keys live in Settings (stored in your OS keychain, never in the project file); flows are composed in the Toolbox's Flows tab; plugins install from the Plugins registry.

Everything you configure is written to a portable kapi.yaml recipe file. Commit it to git to share with your team, reopen it in Kapi Desktop, or run it from the command line:

kapi up -p kapi.yaml

Next Steps​