Problem
AgentMemory exposed MCP slot tools even when AGENTMEMORY_SLOTS was disabled. Calling memory_slot_list then triggered an unregistered function and returned HTTP 500.
Diagnostics also classified sessionless global memories as missing project scope and suggested a migration that could not infer a project (ambiguous result).
The full unit test suite additionally had Windows-only failures caused by Unix path literals, HOME-only test sandboxes, and the Windows iii.exe suffix.
Expected behavior
- Disabled slot tools return an actionable MCP response instead of HTTP 500.
- Sessionless memories are treated as intentionally global.
- Session-linked unscoped memories still produce the migration warning.
- The unit test suite passes on Windows and Unix-compatible path behavior remains covered.
Validation
npm testnpx tsdowngit diff --check- Live
/agentmemory/health, diagnostics, and memory_slot_list
Problem
AgentMemory exposed MCP slot tools even when
AGENTMEMORY_SLOTSwas disabled. Callingmemory_slot_listthen triggered an unregistered function and returned HTTP 500.Diagnostics also classified sessionless global memories as missing project scope and suggested a migration that could not infer a project (
ambiguousresult).The full unit test suite additionally had Windows-only failures caused by Unix path literals,
HOME-only test sandboxes, and the Windowsiii.exesuffix.Expected behavior
Validation
npm testnpx tsdowngit diff --check/agentmemory/health, diagnostics, andmemory_slot_list