memU

Install

npx skillfoxx add skills/memu

npx skills add nevamind-ai/memu --skill install-memu -a claude-code -y

npx skills add nevamind-ai/memu --skill install-memu -a cursor -y

npx skills add nevamind-ai/memu --skill install-memu -a github-copilot -y

npx skills add nevamind-ai/memu --skill install-memu -a codex -y

npx skills add nevamind-ai/memu --skill install-memu -a gemini-cli -y

npx skills add nevamind-ai/memu --skill install-memu -a cline -y

npx skills add nevamind-ai/memu --skill install-memu -a roo -y

npx skills add nevamind-ai/memu --skill install-memu -a opencode -y

pip install --upgrade memu-cli

This is third-party code. Review the repository files before installing.

What it does

memU gives an agent shared memory across sessions, hosts and devices. It installs beside the agent as a set of memu-cli adapters: a scheduled background task reads the session history, and the agent itself turns it into short notes and reusable Markdown skills. Before answering, the agent runs retrieve and pulls in what is relevant to the current task, and a standing instruction in the host file (CLAUDE.md, AGENTS.md and similar) triggers this automatically. Memory lives locally in SQLite or Postgres, or in MemU Cloud, and one configured backend is shared by every connected agent. Setup is driven by the bundled SKILL.md: it detects which host you are, installs the package, prints the built-in guide and walks it step by step with verify gates.

Who it is for. For developers who work in coding agents daily and want context and learnings to persist across sessions and tools.

Example request

Read memU's SKILL.md and set up memory for this agent, keep the backend local

Limitations

memU installs a scheduled background task, reads session history files and edits the host instruction file, and in cloud mode sends derived memory to MemU Cloud. Local mode needs an embedding provider and its key: openai by default, with jina, voyage, doubao and openrouter as alternatives. The support matrix varies by agent and operating system, and some modes are marked as working with limitations. Concurrent access and large stores need Postgres with pgvector.

How to disable. Ask the agent to read SKILL.md and follow the uninstall flow, or run <your-binary> docs uninstall. It removes the scheduled task and the instruction block; the memory store and ~/.memu/config.env are kept by default, and memory is erased only on explicit request.

Security check

• Reads the agent's session history and edits the host instruction file
• Registers a scheduled background task and in cloud mode sends derived memory to MemU Cloud

README in short

The README describes memU as a lightweight agent memory system with a store shared across sessions, hosts and devices. It works through adapters for Codex, Claude Code, Cursor, OpenClaw, Hermes, WorkBuddy, Cola and pi, with a memu-agent detect command for other agents. Each adapter binds two seams: recording history into memory and injecting memory through the host instruction file. The package installs via pip, npx or uvx; memory lives in SQLite, Postgres or MemU Cloud; and the chosen provider computes embeddings. Apache-2.0 licensed, with the core memory logic in roughly 500 lines.

SKILL.md

---
name: install-memu
description: Install or uninstall memU for whatever agent you are — identify your host, print its packaged guide, and follow it to wire (or unwire) both seams (record and inject). Use when the user asks to install, set up, integrate, remove, or uninstall memU.
---

# Install memU

> **Audience: the agent.** A user has pointed you at this file ("read SKILL.md
> and follow it to install memU"). This skill does not contain the install
> steps — it routes you to the right guide, which ships inside the memU package
> and is always in sync with the installed code. Do not install from memory or
> from blog posts; print the guide and follow it to the letter.

memU integrates with a host agent through two seams: **record** (a scheduled
bridging task mines your session log into durable memory) and **inject** (a
standing instruction in your instruction file makes you retrieve before
answering). Each supported host has its own adapter binary carrying its own
install guide. Your job here is three steps: install the package, pick your
binary, print and follow its guide.

## Step 1 — install the package

```
pip install --upgrade memu-cli
```

Related