You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.env.example describes AGENTMEMORY_SLOTS and MAX_OBS_PER_SESSION incorrectly #1484
On main 007a1a7 (0.9.30), two comments in .env.example describe behavior the code does not have. Operators copy this file to ~/.agentmemory/.env (onboarding does it automatically), so the comments read as the contract.
Reproduction and results
.env.example line 165: # AGENTMEMORY_SLOTS=memory # Comma-separated plugin slot names the CLI should claim. isSlotsEnabled() accepts only the exact string true. Following the comment (AGENTMEMORY_SLOTS=memory, or any list of names) leaves slots off while the .env looks configured.
.env.example line 127: # MAX_OBS_PER_SESSION=500 # Per-session observation cap before consolidation kicks in.
Reaching the cap does not start consolidation. mem::observe refuses every further observation of that session with Session observation limit reached (500), and capture parks each one as a dead letter.
Required behavior
The AGENTMEMORY_SLOTS comment says the value must be true and names what it enables.
The MAX_OBS_PER_SESSION comment says it is a hard per-session write limit, that later observations are refused, and that 0 disables the cap.
Acceptance checks
Comments match isSlotsEnabled() and the cap branch in mem::observe. npm run docs:check and npm run skills:check stay green.
Activity