mem0-status

Diagnoses mem0 plugin connectivity, API key validity, and memory read/write functionality.

64.5k|7.6k|Updated Jun 20, 2023
One-click install
npx skills add https://github.com/mem0ai/mem0 --skill mem0-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mem0-status
Source: https://github.com/mem0ai/mem0/tree/main/integrations/mem0-plugin/.opencode-plugin/opencode-skills/mem0-status
Command: npx skills add https://github.com/mem0ai/mem0 --skill mem0-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When memory operations fail, searches return empty results, or add_memory calls error out, it is hard to tell whether the cause is a missing API key, a broken session hook, or a connectivity issue. This Skill runs a structured diagnostic across the entire mem0 plugin stack and reports exactly which component is failing.

Core Features & Use Cases

  • Six-point health check: Validates the MEM0_API_KEY, identity resolution (user_id, project_id, branch), memory tool connectivity via search_memories, write capability via add_memory with cleanup, session context injection, and auto-dream gate eligibility.
  • Deep memory quality scan: With the --deep flag, detects duplicate memories, stale entries, low-confidence facts, contradictions, and untagged orphan memories across the project store.
  • Use Case: After installing the mem0 OpenCode plugin, your memories are not being recalled. Run the status check to discover the shell.env hook never fired, so MEM0_APP_ID is empty, and restart OpenCode to fix it.

Quick Start

Ask the assistant to run a mem0 status diagnostic to verify the plugin is configured and working correctly.

Frequently Asked Questions about mem0-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot mem0 memory operations that are failing?

Run the mem0-status diagnostic, which checks the API key, identity resolution, memory tool connectivity, write capability, and session context in sequence. It reports PASS, WARN, or FAIL for each check and adds a troubleshooting section with specific fix steps for any failure.

Why does mem0 search return empty results in OpenCode?

Empty results often mean the shell.env hook did not fire, leaving MEM0_APP_ID or MEM0_USER_ID unset so filters match nothing. The status check warns when project_id is empty and recommends restarting OpenCode to re-trigger the hook.

How do I check if my MEM0_API_KEY is configured correctly?

The diagnostic reads the MEM0_API_KEY environment variable and prints only its first six characters to confirm it is set without exposing the secret. If it reports NOT_SET, you need to configure the key before memory tools will work.

Can I detect duplicate or stale memories in mem0?

Yes, invoke the status check with the --deep flag to run a memory quality scan. It flags duplicate pairs, stale session_state entries older than 90 days, low-confidence memories, contradictions, and untagged orphans, and suggests running /mem0-dream to fix them.

Why is mem0 auto-dream consolidation not running?

Auto-dream only runs when three gates pass: enough hours since last consolidation, enough sessions since, and enough project memories. The status check reads ~/.mem0/mem0-dream-state.json and settings.json to show exactly which gate is blocking, such as sessions 2/5.