Gå til hovedinnhold

A guided tour

Kapi 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). This tour walks each surface in motion; for what the app is and how to install it, see the overview.

Create and manage a project​

A project pairs a source language with the locales you translate into, the files in scope, and the flows that process them. Naming it is the only required step — everything else is configured visually. The project home leads with ship readiness: per-locale coverage and each scope's ship-gate standing, with Bring up to date to run the default flow until every gated scope is shippable or parked — a plan pre-flight shows the pending work and a rough token estimate before anything runs. What parks lands in the Review surface; manual run pickers sit under an Advanced disclosure.

Outdated recording

The interface has changed since this was recorded. The workflow it demonstrates still applies, but some screens and labels differ from the current release. The project home now leads with the convergence hero and its active-model badge.

Manage content in a project​

A project's content is the set of files it translates. Glob patterns are grouped into named collections — documentation, store UI, contracts, templates — each mapping source files to their translated counterparts. The project home shows content as one card per collection — the patterns alongside the real files they match and the format Kapi detected for each.

Opening a file previews it the way the engine parses it: a Preview of the rendered document with the source ↔ target toggle, a Blocks list, and — where the format carries them — a Structure view (roles, reading order) and a Layout view (page-scaled bounding boxes). For media, a Media tab renders the asset itself: an image with its OCR boxes overlaid, or an audio/video player with the recognized cues as a synced subtitle track and on-screen frame text shown at its timecode. Opening an image, audio, or video file offers to install the engine plugin it needs (kapi-vision / kapi-asr / kapi-av) on first use.

Compose flows​

A project's flows are the pipelines it runs over its content — a plain AI translation, a translation followed by quality checks, a pseudo-translation for testing. Flows live as a tab in the Toolbox; each is a named sequence of steps, saved alongside the project and shared through version control. Open one to see and edit its pipeline.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Configure appearance, providers, and plugins​

Settings gather everything in one place: light or dark appearance, the AI providers Kapi translates with (keys stay in your OS keychain), and the plugins that extend its formats and tools.

Outdated recording

The interface has changed since this was recorded. The workflow it demonstrates still applies, but some screens and labels differ from the current release. The sidebar now reads Terms and Content Memory, and AI Models shows which model runs are using.

Browse terminology and content memory​

Kapi keeps a store of approved multi-locale terms and a memory of past translations. Both are searchable, with inline formatting and entity placeholders preserved.

Extend with plugins​

Plugins extend Kapi with new formats and engines — the kapi-sat segmenter for ML sentence segmentation, the kapi-pdfium PDF reader, the kapi-vision OCR engine, and the kapi-asr transcriber. Install one from the registry in one click, and the formats and tools it adds appear in the project immediately; the manage plugins recipe walks the flow step by step.

Works with Bowrain

The kapi-bowrain plugin (brew install neokapi/tap/bowrain-cli) is a CLI-side plugin in the same registry: it adds the project-sync commands (kapi push, kapi pull) for projects whose recipe declares a server: block, connecting them to a Bowrain server — a hosted, shared memory, terminology, and review surface for a team and its agents. See the Bowrain documentation.

Next​