Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs(security): note that backups carry config.toml
AkitaOnRailsb4b1aa9e617c
diff --git a/SECURITY.md b/SECURITY.mdindex 7a6077c4..565dd3af 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -44,6 +44,12 @@ what the project is and is not designed to defend against.spool is capped at 10,000 files. `ai-memory backup` does not include thespool, but a filesystem-level copy of the data directory does.+ An `ai-memory backup` archive includes `<data_dir>/config.toml` verbatim,+ which may hold the API-key pepper and other inline credentials; protect+ the archive as a secret (see+ [`docs/lifecycle-ops.md`](docs/lifecycle-ops.md#backup)). `restore` keeps+ an existing live config unless `--with-config` is passed.+- **Network exposure when binding to non-loopback addresses.** If you run`ai-memory serve --bind 0.0.0.0:…` you are exposing the MCP and adminroutes to your local network. Protect this with: