xmemo
XMemo — user-owned long-term memory for AI agents. Store and recall memories across sessions, tools, and CLIs.
Open source Open in the app JSON README (API)
About
XMemo — user-owned long-term memory for AI agents. Store and recall memories across sessions, tools, and CLIs.
Details
- Kind
- Plugins
- Topic
- AI, RAG & memory
- Publisher
- yonro
- Origin
- gemini
- Category
- ferramentas
- Version
- 0.1.0
- Last push
- 2026-05-29T17:16:36Z
- Repository state
- ativo
- License
- MIT
- Added
- 2026-08-30 14:13:39
- Updated
- 2026-08-30 14:13:39
- Origin id
yonro/xmemo-gemini-cli
README
# XMemo for Gemini CLI [](https://geminicli.com/extensions/browse/) **XMemo** gives Gemini CLI a persistent, user-owned long-term memory. Store and recall facts, preferences, decisions, and project context across sessions — and share the same memory with every AI tool you use (ChatGPT, Claude, Copilot, IDEs, and more). XMemo is **user-owned**: you control, view, edit, and delete your memories at [xmemo.dev](https://xmemo.dev). ## Install ```bash gemini extensions install https://github.com/yonro/xmemo-gemini-cli ``` After installing, **restart your Gemini CLI session** so the extension loads. ## Sign in (OAuth — no token needed) XMemo uses **automatic OAuth**. The first time the `memory_os` tools are used, Gemini CLI detects the `401` from `https://xmemo.dev/mcp`, discovers XMemo's OAuth endpoints, registers a client, and opens your browser to sign in. Your tokens are stored securely by Gemini CLI for future sessions — **no API key to copy or paste.** > Prefer an API token instead? You can add `"Authorization": "Bearer <token>"` to > the `headers` block manually, but OAuth is the recommended, zero-secret path. ## What you get - A `memory_os` MCP server connected to `https://xmemo.dev/mcp`. - Tools to **search**, **add**, and **update** memories from inside Gemini CLI. - A `GEMINI.md` playbook that teaches the model when to store and recall memories. ## How it works | Field | Value | | --- | --- | | Transport | Remote HTTP MCP (`httpUrl`) | | Endpoint | `https://xmemo.dev/mcp` | | Auth | Automatic OAuth 2.0 (RFC 9728 discovery + dynamic client registration + PKCE) | | Agent label | `X-Memory-OS-Agent-ID: gemini-cli` (so memories are attributed to this client) | OAuth authenticates **you** (the memory owner). The `X-Memory-OS-Agent-ID` header is a label that tells XMemo which client wrote a memory — it is attribution, not a security boundary. Your OAuth identity is the security boundary. ## Manage the extension ```bash gemini extensions list gemini extensions update xmemo gemini extensions disable xmemo gemini extensions uninstall xmemo ``` ## Privacy - Authentication uses OAuth; tokens are managed by Gemini CLI, not stored in this repo. - No host environment variables are forwarded to the server. - You can delete any memory at any time from [xmemo.dev](https://xmemo.dev). ## Links - Website: https://xmemo.dev - MCP endpoint: https://xmemo.dev/mcp ## License MIT — see [LICENSE](LICENSE).