Gå til hovedinnhold

Installation

neokapi ships two artifacts you can install independently:

  • the kapi CLI — a single self-contained binary that runs offline by default and operates directly on your files;
  • Kapi Desktop — the visual companion app, which bundles the CLI.

The two sections below cover each. If you only want the command line, you need the first section alone.

Install the Kapi CLI​

Once you've tried kapi in the browser, install the binary to run it locally against your own files.

Recommended right now: the beta channel

kapi 1.2.0 is in its release-candidate phase and has no stable release yet, so the beta channel is the recommended way to install today — it carries the current build (the latest release candidate) and, once 1.2.0 ships, every stable release too. The plain stable formulae still track the previous stable, which is behind 1.2.0. The Homebrew commands below show the beta install first; see Beta channel for switching an existing install. Once 1.2.0 stable ships, the stable formulae become the recommendation again.

Homebrew (macOS/Linux)​

Until 1.2.0 stable ships, install the beta formula (the current build):

brew install neokapi/tap/kapi-cli-beta

Once 1.2.0 stable is released, the stable formula is the default:

brew install neokapi/tap/kapi-cli

WinGet (Windows)​

winget install Neokapi.KapiCli

Binary Downloads​

Pre-built binaries for all platforms are available on the GitHub Releases page.

Direct downloads for kapi 1.2.0-rc13 (CLI):

macOS (Apple Silicon)

Linux

Windows (Authenticode-signed, portable zip)

Verify a download against checksums.txt.

Verify the install​

kapi version

Connect an AI (optional)​

The rule-based commands — pseudo-translate, stats, brand checks against a profile file — need no AI at all. For LLM-backed translation, QA, and review, one command finds what you already have and confirms it:

kapi models setup

Setup detects the AI options on your machine — the Claude Code CLI (uses your Claude subscription, no API key), a running Ollama server, and API keys already in your environment — then verifies your pick with a small test call and saves it as the default, shared with Kapi Desktop. Usually that's one confirm, not a key paste. To store a key explicitly (or in CI, where a key is the right choice), use kapi credentials add <name> --provider <p> --api-key … — keys live in your OS keychain. See Use with Claude for the subscription option and the Quick Start for what to run next.

Install Kapi Desktop​

Kapi Desktop is the visual companion to the CLI. Each package below installs the kapi CLI as a dependency, so a single install covers both. See the Kapi Desktop overview for what it does.

macOS (Homebrew)​

Until 1.2.0 stable ships, install the beta cask (it pulls kapi-cli-beta automatically):

brew install --cask neokapi/tap/kapi@beta

Once 1.2.0 stable is released, the stable cask is the default:

brew install --cask neokapi/tap/kapi

Direct downloads (Windows, macOS, Linux)​

The Windows installer is Authenticode-signed and registers a Start-menu entry and uninstaller. Direct, version-pinned links are listed below; the full set is always on the GitHub Releases page.

Direct downloads for Kapi Desktop 1.2.0-rc13:

macOS (Apple Silicon)

Windows (signed installer)

Linux

Beta channel​

The beta channel is a fast ring: it receives release candidates and every stable release, so a beta install is never behind stable — it just gets things sooner. While 1.2.0 is in release candidates, it is the recommended channel (see above); once 1.2.0 stable ships it returns to being an opt-in early-adopter ring. It ships as separate Homebrew packages.

Beta and stable install the same kapi binary (and the same app), so they are mutually exclusive: you switch channels rather than run both side by side. Trying to install one while the other is present is rejected by Homebrew.

A fresh install just uses the beta commands above (brew install neokapi/tap/kapi-cli-beta, or --cask neokapi/tap/kapi@beta); the steps below are for switching an existing stable install to beta.

Switch to beta​

brew update
# Remove the stable packages (the desktop cask depends on the CLI formula).
brew uninstall --cask neokapi/tap/kapi
brew uninstall neokapi/tap/kapi-cli
# Install the beta packages — the cask pulls kapi-cli-beta automatically.
brew install --cask neokapi/tap/kapi@beta

For the CLI only, skip the cask: brew install neokapi/tap/kapi-cli-beta. kapi-pdfium is a shared dependency with no beta variant — leave it installed.

A beta build is clearly marked: kapi version prints a (beta) badge, and the desktop window title reads Kapi (Beta). For direct downloads, beta builds are the assets attached to the Pre-release entries on the Releases page.

Stay current, or switch back​

brew upgrade kapi-cli-beta                          # newer beta builds
# Back to stable:
brew uninstall --cask neokapi/tap/kapi@beta
brew uninstall neokapi/tap/kapi-cli-beta
brew install --cask neokapi/tap/kapi

The chosen channel is remembered across updates (kapi pins it on first run, shared by the CLI and the desktop app). Set KAPI_UPDATE_CHANNEL=beta (or stable) to override it for a single shell.

Beta packages are a Homebrew concept (separate formula/cask). WinGet tracks the stable release. The version-pinned direct downloads above point to the current release — during the 1.2.0 release-candidate phase that is the latest RC (a beta build); the full set, including any stable, is on the Releases page.