Skip to main content

Install

The installer puts the binary in ~/.korve/bin/korve (override with KORVE_INSTALL_DIR) and tells you if that directory needs adding to your PATH. Published binaries: macOS on Apple Silicon (darwin-arm64), Linux x86-64 (linux-x64), and Linux ARM64 (linux-arm64). The installer fails with a source-build command on unsupported systems. Verify:

Authenticate interactively

The primary sign-in path is browser OAuth with PKCE:
The CLI opens a browser authorization page and listens on a random literal 127.0.0.1 callback port. It stores the resulting short-lived access token and rotating refresh token in ${KORVE_CONFIG_DIR:-~/.config/korve}/oauth-credentials.toml, with 0600 permissions. Non-secret organization, grant, and API URL metadata live separately in ~/.config/korve/config.toml; a legacy API key, when used, is stored there with 0600 permissions. korve logout removes the stored login material. See Agent OAuth. For unattended CI, a legacy organization API key remains supported:

Configuration precedence

Every setting resolves the same way — explicit beats ambient: For CI, skip persisted login and set KORVE_API_KEY + KORVE_ORG in the environment. Never copy a local OAuth refresh token into CI. OAuth grants deliberately stop at admin. Commands backed by owner-only operations (for example destructive project deletion) fail locally with an explicit instruction to use a separately revocable organization API key.

Shell completions

Next