Menü
Use XMemo from VS Code (and forks like Cursor/Windsurf) to recall project context, capture engineering decisions, preserve handoff state, and connect to the hosted XMemo MCP endpoint safely.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Persistent user-owned memory for agents with standalone runtime execution. Use when an agent should remember, recall, search memory, save or restore handoff state, manage TODOs, record expenses, diagnose XMemo auth, or operate XMemo even when MCP tools are not configured.
Use XMemo's hosted MCP memory tools for durable context, project preferences, decisions, reminders, and cross-session recall in Cursor.
Basierend auf der SOC-Berufsklassifikation
| name | xmemo-vscode |
| description | Use XMemo from VS Code (and forks like Cursor/Windsurf) to recall project context, capture engineering decisions, preserve handoff state, and connect to the hosted XMemo MCP endpoint safely. |
Use this skill when an editor task should use XMemo memory: restore project context, save durable decisions, record working state, or prepare a clean handoff.
Your editor executes development. XMemo lets it remember the project.
XMemo is a user-owned, identity-aware memory layer for multi-agent workflows. It carries useful project context, decisions, preferences, and progress across ChatGPT, Codex, Claude, Cursor, Copilot, Gemini, IDEs, CLIs, and other agents.
Hosted MCP endpoint: https://xmemo.dev/mcp
The extension authenticates with a token stored in the OS keychain (VS Code SecretStorage) and attributes activity with:
X-Memory-OS-Agent-ID: vscodeX-Memory-OS-Agent-Instance-ID: <local-instance-id>OAuth 2.0 (PKCE) in-editor sign-in is the default; token paste is a documented fallback for power users.
At task start: recall focused context for the current repo/subsystem/task; restore a restart snapshot if continuing prior work; fall back to repository evidence if XMemo is unavailable.
During architecture/integration work: capture pending decisions before major tradeoffs; resolve them after implementation or explicit confirmation; save only durable conclusions, not noisy intermediate reasoning.
At handoff: update working state (what changed, what was verified, what remains); create memory TODOs for concrete follow-ups; create a restart snapshot when work is incomplete.
X-Memory-OS-Agent-ID and instance ID as non-secret attribution metadata, not authentication.