headroomlabs-ai/headroom · error · RuntimeError
Memory system not initialized
Error message
Memory system not initialized
What it means
Error "Memory system not initialized" thrown in headroomlabs-ai/headroom.
Source
Thrown at headroom/evals/memory/runner.py:361
except Exception as e:
logger.warning(f"Memory extraction failed: {e}")
return []
async def _store_conversation(
self,
conversation: LoCoMoConversation,
) -> int:
"""Store a conversation's dialogues as memories.
Args:
conversation: The LoCoMo conversation to store.
Returns:
Number of memories stored.
"""
if self.memory is None:
raise RuntimeError("Memory system not initialized")
memories_data: list[dict[str, Any]] = []
user_id = f"locomo_{conversation.sample_id}"
if self.config.extract_memories:
# Use LLM to extract facts from each session
for session in conversation.sessions:
session_id = f"session_{session.session_num}"
# Get full session text
session_text = session.text
# Extract memories using LLM
extracted = self._extract_memories_from_session(
session_text=session_text,
session_datetime=session.datetime,
speaker_a=conversation.speaker_a,
speaker_b=conversation.speaker_b,View on GitHub (pinned to 322425c43b)
Solutions
- Initialize the memory system before running the eval (call the runner's setup/init step or pass an initialized memory instance)
- Check earlier initialization errors — a failed backend or missing dependency can leave the memory system uninitialized
- Verify memory backend configuration (storage path, embedder) is valid
When it happens
Trigger: Raised when the memory eval runner is asked to use the memory system before it has been initialized, usually because setup was skipped or failed earlier.
Common situations: See trigger scenarios.
AI-assisted analysis of headroomlabs-ai/headroom@322425c43b (2026-08-15).
Data as JSON: /api/errors/9c95a047f71a6e7f.
Report an issue: GitHub.