Skip to content

.env.example describes AGENTMEMORY_SLOTS and MAX_OBS_PER_SESSION incorrectly #1484

Open

Description

@Rex57

Current-main boundary

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

  1. .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.
  2. .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.

Source and existing work

.env.example L127, .env.example L165, isSlotsEnabled, observe cap.

#888 and PR #894 cover the MCP error when slots are off; neither changes .env.example.

Environment: agentmemory 0.9.30, Node v26.10.0, macOS 27.0.1 (arm64).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions