mem0-status

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

Empty results often mean the MEM0_APP_ID or MEM0_USER_ID environment variables were not injected because the plugin's shell.env hook did not fire. The status check warns when project_id is empty and recommends restarting OpenCode.

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. A missing key is reported as a FAIL with a clear message.

It evaluates whether memory consolidation is eligible to run by comparing time since last consolidation, sessions since, and project memory count against the minHours, minSessions, and minMemories thresholds in ~/.mem0/settings.json. Blocking gates are reported as informational warnings, not errors.

Invoke the status check with --deep to run a memory quality scan. It flags duplicate pairs with high textual overlap, stale session_state memories older than 90 days, low-confidence entries, contradictions, and untagged orphan memories.