Start
Stop
Watch
Status
- Whether Kairos is active
- Workspace, latest activity, last outcome
- Account validity
- Recent memory growth
- Pending dream-bucket items
Authentication
login after an account switch, or when backant start reports that the account check failed. Credentials persist across reboots under ~/.claude/kairos/.
Per-workspace vs. user-level state
Memory is intentionally user-level rather than per-workspace — observations about one codebase often inform decisions about another (e.g. “the team uses Zod everywhere”). If you want strict per-workspace isolation, override
KAIROS_MEMORY_DB to a workspace-local path before starting.
Configuration reload
Changes to.backant.toml take effect on the next turn. The daemon rebuilds its permissions block from the file before every turn, so no restart is needed. --fresh is only for discarding in-process judgment; it does not affect policy.
See Configuration for the full .backant.toml schema, and Let your agent run Kairos for changing keys through backant ctl config.
Steering, configuring, and tasking
backant ctl is the control plane. Every verb takes --json and answers with one envelope line, which is what host agents and scripts use.
backant tui wraps the same verbs in an interactive view. Install the skill (backant skill install --all) and your coding agent drives these for you; see Let your agent run Kairos.
Quick reference
--help on any subcommand for flags and arguments.