install-memu
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.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 14 427
- Лиценз
- NOASSERTION
- Последна проверка на записа
- 20.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add NevaMind-AI/memUСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
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
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.
This puts memu and every host-adapter binary on PATH. If pip is not the
right tool for this machine (managed Python, uv-only), use the equivalent —
what matters is that the binaries below resolve from a bare, non-interactive
shell. With uv this means uv tool install --upgrade memu-cli, not
uv pip install: however it is installed, memu-cli is a cross-session
bridging tool and must be callable everywhere, not scoped to one project venv.
Step 2 — pick your host binary
Identify which agent you are (not which agents are installed — the one executing this skill):
| You are | Your binary |
|---|---|
| Codex | memu-codex |
| Claude Code | memu-claude-code |
| Cursor (Agent/CLI) | memu-cursor |
| OpenClaw | memu-openclaw |
| Hermes Agent | memu-hermes |
| WorkBuddy | memu-workbuddy |
| Cola | memu-cola |
| pi | memu-pi |
| anything else | memu-agent |
Unsure, or not in the table? You are memu-agent. Run:
memu-agent detect