Quick install
From inside the repo you want Kairos to work on:Kairos works at the workspace level. Each repo gets its own
.backant.toml policy file and its own daemon. Memory itself lives at the user level (under ~/.claude/kairos/) and is shared across all workspaces.Requirements
The first-run wizard
npx backant-kairos runs these steps in order. Each step is also runnable individually as a subcommand.
1
Login
Opens a browser auth flow against backant.io to issue credentials. Credentials persist across reboots under
~/.claude/kairos/.2
Project setup
Scans the workspace, detects language/framework/CI conventions, and generates Idempotent — existing
.backant.toml (the per-project policy file). Also installs recommended skills and plugins, and adds .backant.toml to CODEOWNERS so policy changes route to you..backant.toml is preserved.3
Memory init
One-time installation of the local embedding stack. Pulls the Docker image plus a Qwen3-Embedding model sized to your hardware, and writes Takes 3–5 minutes depending on the tier and your network. See the memory page for tier sizing.
~/.claude/kairos/config.json.4
Start Kairos
Attaches Kairos to the current workspace and begins working.
Subsequent installs
Once the wizard has run once per workspace, you only needbackant start to resume. Running backant alone detects whether to resume or run setup.
Re-running setup
If you change.backant.toml, add a new repo, or want to refresh installed skills:
Switching embedding models
After the initial install, you can re-runmemory init to pick a different Qwen3 tier. If you do, run memory reindex afterwards to re-embed everything against the new model — otherwise recall will produce dimension mismatches.
Uninstall
To stop the daemon and remove all Kairos state from your machine:npm uninstall -g backant-kairos if installed globally, or just deleted if you used npx.