Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(readme): list allowlist mode beside capture exclusions
AkitaOnRails612eec402161
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 6fe428f8..4014ed78 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -95,6 +95,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0`capture_mode`, `marker_present` and `admits_capture` so an opt-out can beverified without sending anything. Default behaviour is unchanged, and`--capture-mode denylist` restores it.+- Documented allowlist mode in the README feature list beside the existing+ per-repository capture exclusions, so the two capture controls are+ discoverable from the same place (#446).- Corrected the allowlist-mode documentation, which claimed "every agent'shook honours it". The gate runs inside the native `ai-memory hook` binarybefore the spool write, so script-based installs — thediff --git a/README.md b/README.mdindex 2283a009..26766a14 100644--- a/README.md+++ b/README.md@@ -93,6 +93,11 @@ priors are at the [bottom](#influences-and-prior-art).- **Per-repository capture exclusions.** A nearest-marker `[capture]``ignore_paths` policy drops matching recognized file-tool events before theyreach the local spool or server. See [the capture policy reference](docs/marker-file.md#capture-exclusions).+- **Opt-in capture scope.** `install-hooks --capture-mode allowlist` inverts+ the default so a repository without a marker emits no lifecycle event at+ all, dropped by the native hook before the spool. Forgetting a marker then+ costs recall rather than confidentiality. Enforced by native `ai-memory+ hook` commands only — see [allowlist mode](docs/marker-file.md#allowlist-mode-the-marker-as-an-opt-in).- **Optional per-operator memory slots.** On shared servers,`[slots] per_user = true` keeps engine-written `_slots/` context in a boundednamespace derived from the authenticated operator. Session briefs and