Skip to content
KurrentDB

sessions, recap, errors, validate-plan, set-title

For recap, errors, validate-plan and eval, an omitted session id is resolved from KCAP_SESSION_ID, then CODEX_THREAD_ID; pass one explicitly outside an agent session. recap and errors accept a session id or its readable slug; per-turn commands need the id

Terminal window
kcap sessions [--active|--ended|--all] [--mine] [--repo <owner/name|hash>] [--touching <path>] [--limit <n>] [--json]

Default: active sessions in the current checkout’s repository, 20 rows. --touching matches stored edit and write attempts on a path (not edits made through a shell command)

Terminal window
kcap recap [<session>] [--chain] [--full]
kcap recap --repo
kcap recap --per-turn <session>
kcap recap --get-turn <N> <session>

The default recap is the stored plan, the outcome summary and a per-turn outline. --full prints the transcript; --chain includes continuations; --repo lists recent summaries for this repository; --per-turn lists turns with indexes and --get-turn prints one in full

Terminal window
kcap errors [<session>] [--chain]

The failed tool calls, grouped. An error may have been recovered later in the session

Terminal window
kcap validate-plan [<session>]

Prints the declared or discovered plan artifacts, the task ledger with statuses, available outcome summaries and the stored work, with instructions for an agent to compare them. Exit 0 includes “no plan found”; 1 is a server or access error; 2 means the leading plan artifact’s content is unavailable. Exit 0 is not a completion verdict

Terminal window
kcap set-title "Fix the checkout regression"
kcap generate-whats-done <session> [--codex]

set-title names the current session (from the environment only; no id argument; titles over 120 characters are shortened). generate-whats-done generates and stores an outcome summary with local Claude, or Codex with --codex; diagnostics go to ~/.config/kcap/logs/<session>-whatsdone.log