refactor(plugin): rename mem0-codex skill to mem0-mcp

The skill content is runtime-agnostic — same protocol applies to Claude
Code, Cursor, and Codex. The "codex" name was a vestige from when Codex
was the only runtime delivering this guidance via skill (because Codex
didn't have hooks yet). Now all three runtimes run the same hook plus
load the same skill, so name it after the surface it actually documents:
the mem0 MCP tool protocol.
This commit is contained in:
gabrielstein-mem0
2026-04-30 15:29:19 -07:00
parent efd33d9791
commit 875eedfbac
@@ -1,13 +1,14 @@
---
name: mem0-codex
name: mem0-mcp
description: >
Mem0 persistent memory integration for Codex. Decide deliberately when memory
context would help, run targeted searches with metadata filters when it would,
and store key learnings as work completes. Use the mem0 MCP tools (add_memory,
Mem0 memory protocol for agents using the mem0 MCP tools (Claude Code, Cursor,
Codex, and any other MCP-aware runtime). Decide deliberately when memory context
would help, run targeted searches with metadata filters when it would, and store
key learnings as work completes. Use the mem0 MCP tools (add_memory,
search_memories, get_memories, etc.) for all memory operations.
---
# Mem0 Memory Protocol for Codex
# Mem0 MCP Memory Protocol
You have access to persistent memory via the mem0 MCP tools. Follow this protocol to maintain context across sessions.