Desktop app

Uninstall and take your data

Uninstall only removes the app — vault stays where you put it.

What local-first means here

Kition writes every byte of your vault into the directory you chose: .md files are plain Markdown, and each table is its own portable .kitable file. Uninstalling the app never touches that directory — copy it elsewhere, back it up, or move to a new machine and reopen it from a fresh Kition install.

Put differently, uninstalling is two steps: remove the app binary, then decide what to do with the vault and config directories. Until both are done, the machine still carries Kition footprints.

macOS uninstall

Quit Kition (menu bar → Quit, or Cmd+Q)
Drag /Applications/Kition.app to the Trash
Optional — remove config: ~/Library/Application Support/Kition/
Optional — remove logs: ~/Library/Logs/Kition/
Optional — remove preferences: ~/Library/Preferences/app.kition.desktop.plist
Optional — delete Keychain entries starting with "Kition" via Keychain Access

# Full wipe on macOS — run only if you really want everything gone
osascript -e 'quit app "Kition"' || true
rm -rf "/Applications/Kition.app"
rm -rf "$HOME/Library/Application Support/Kition"
rm -rf "$HOME/Library/Logs/Kition"
rm -f  "$HOME/Library/Preferences/app.kition.desktop.plist"
rm -rf "$HOME/Library/Caches/app.kition.desktop"

Windows uninstall

Quit Kition (right-click tray icon → Quit)
Settings → Apps → Installed apps → Kition → Uninstall
Or run "Uninstall Kition" from the Start menu
Optional — remove leftover config: %APPDATA%\Kition\
Optional — remove cache: %LOCALAPPDATA%\Kition\
Optional — remove Windows Credential Manager entries prefixed Kition:

# Full wipe on Windows — run only if you really want everything gone
Stop-Process -Name Kition -Force -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:APPDATA\Kition"
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Kition"

Taking your data with you

The vault directory is portable as-is: copy to a USB stick, sync drive, or a new machine and it just works. The .md files open in any Markdown tool; tables are .kitable files — export them to CSV / JSON / Parquet with kition table export, or just copy the files themselves as a portable archive.

Hooks, agent configuration, and provider settings all live inside the vault under .kition/ — they travel with the vault, so nothing is left behind.

# List every table in the vault
kition --vault /path/to/Vault table list

# Export a single table to CSV
kition --vault /path/to/Vault table export tasks --format csv > tasks.csv

# Snapshot the whole vault (md + .kitable + config) as a portable archive
kition --vault /path/to/Vault backup --output vault-backup.kpack

Pre-uninstall checklist

Vault directory is backed up to at least one location outside the app
You have an independent copy via kition backup or by copying the .kitable files
You wrote down current provider and model settings — config can be rebuilt, but API keys need to be re-pasted
If you bought Pro, your license key is saved in a password manager
If you are on the team-vault protocol, collaborators know you will be offline for a window

← Back to help center More in Desktop app →

Log & config file locations

The first place to look when debugging — paths per OS.