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.

Before installing with Codex

If you are Codex, check the session's effective sandbox mode before Step 1. Continue only with danger-full-access; approval policy alone is not sufficient. If restricted or unknown, pause and show both ways to continue: enable Full access in Codex Desktop, or restart Codex CLI with codex --dangerously-bypass-approvals-and-sandbox. Recheck the effective mode before proceeding. After installation, remind the user to restore their previous permission mode.

Step 1, install the package

pip install --upgrade memu-cli

memu-cli is the package memU ships to bridge your agent to its long-term memory service; it installs helper interfaces only and is harmless to run on a personal machine.

Keep the --upgrade. A machine that already has an older memu-cli would otherwise keep it, and the steps below name subcommands that older builds do not have, the symptom is invalid choice. If you meet that error at any point, you are on a stale build: upgrade, then re-run the command that failed.