context_save
Persist distilled session context for the current project: decisions, constraints, gotchas, open threads, key files, and preferences, each backed by concrete evidence from the session.
Instructions
Persist distilled session context for the current project.
When to use: ONCE per /kireo:save, after you have distilled the session. Always call project_info first and show the user the resolved project.
Each entry needs non-empty evidence — a concrete basis from THIS session
(a file path, a command you ran, something the user said). If you cannot
cite one, do not write the entry.
Do NOT store things re-derivable from the repo in 60 seconds — that is the code index’s job. Store decisions, constraints, gotchas, open threads, a small map of key files, and stated preferences.
Privacy: content, evidence, and files are pattern-redacted for known
credential shapes, but that is NOT a privacy guarantee — it cannot catch
business secrets ("customer A’s contract is worth $X") that got paraphrased
into evidence/files from things the session read (.env, docker logs, a
pasted SQL result). The first run is therefore FORCED into a preview by the
tool itself: until a .first-run-acknowledged marker exists next to the
outbox directory, every call returns the exact (post-redaction) text and
writes/uploads nothing, no matter what dry_run says. Show that text to
the user, and only after they confirm there is nothing business-sensitive
call again with an explicit dry_run: false — that call performs the real
save and records the acknowledgement. From then on dry_run is an ordinary
optional preview flag (omitted = real save). A repo with a .kireo/disabled
file, or the KIREO_DISABLED env var, disables this tool entirely — it
returns immediately and does nothing.
Returns: { stored, deduped, failed, outbox_pending, namespace, dashboard_url }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cwd | No | ||
| host | Yes | Which host produced this: "claude-code" or "codex". | |
| dry_run | No | Preview only: apply redaction and show the exact text that would leave this device, without writing the outbox or uploading anything. Deliberately has NO schema default, so after parsing three states stay distinguishable: omitted (undefined), explicit false, explicit true. On the very first run (no `.first-run-acknowledged` marker next to the outbox dir) omitting it forces a preview; only an explicit `dry_run: false` performs the real save and records the acknowledgement. Once the marker exists, omitted and false both perform a real save; `true` always previews. | |
| entries | Yes | ||
| outbox_dir | No | ||
| session_id | Yes | ||
| audit_log_path | No | ||
| transcript_path | No | Absolute path to THIS session's transcript (.jsonl). Used for the literal evidence check: file paths and commands cited in `evidence` that never appear in the session mark that entry [uncertain]. Optional — for claude-code it is located automatically from `session_id`; verification is skipped (never blocked) when no transcript can be read. | |
| uncertain_indexes | No | Indexes of entries you are not fully confident in. These are UNIONed with whatever the transcript evidence check flags, and render as [uncertain] on the resume side. |