Coding agents forget between sessions. They re-grep the same tree, re-learn the same constraints, and burn tokens rediscovering decisions you already paid for. amem is a private local sidecar so the next session starts oriented.
Anti-poisoning & injection defenses
How does amem prevent poisoned chat or malicious prompt injections from corrupting memory? Ingestion runs through syntactic fact filters (isFactLike), secret deny patterns, quality scoring, and a default staged review queue (ProposalDraft) before anything is applied.
Scope isolation & anti-bleed
Every claim, task, and note is strictly partitioned by repository (repo_id). Context packets are tightly ranked via hybrid BM25 + vector search and hard-capped at 2.4KB to avoid prompt stuffing and cross-project leaks.
Staleness & code drift
Claims are tied to file anchors. If anchored files are edited or deleted, amem automatically marks claims stale, applies a ranking penalty, and warns the model to verify before trusting.
Localhost & zero egress
The daemon strictly binds to 127.0.0.1, telemetry is forced off, and local databases use 0700 permissions with optional AES-256-GCM encryption at rest.