/memory.wiki in your AI tool

The Memory.Wiki skill installer adds a small instruction set to your AI coding tool so capturing, bundling, and pulling your hub URL feels native. Same three actions across Claude Code, Cursor, Codex CLI, and Aider.

Install (one line per tool)

Claude Code

bash
curl -fsSL https://memory.wiki/skills/memory.wiki/install.sh | sh

Drops SKILL.md into ~/.claude/skills/memory.wiki/. Restart Claude Code (or run /reload-skills).

Cursor

bash
curl -fsSL https://memory.wiki/skills/memory.wiki/install.sh | sh -s -- --target=cursor

Drops memory.wiki.mdc into ~/.cursor/rules/. Cursor picks it up on next launch.

Codex CLI

bash
curl -fsSL https://memory.wiki/skills/memory.wiki/install.sh | sh -s -- --target=codex

Appends a memory.wiki actions block to ~/.codex/AGENTS.md. Idempotent: rerunning replaces just the Memory.Wiki block, leaves the rest of your AGENTS.md alone.

Aider

bash
curl -fsSL https://memory.wiki/skills/memory.wiki/install.sh | sh -s -- --target=aider

Drops conventions.md into ~/.aider/. Add read: ~/.aider/conventions.md to your .aider.conf.yml.

What it does, once installed

The same three verbs in every tool:

Action	Trigger	Result
Capture	"save this to memory.wiki", `/memory.wiki capture <title>`	Current conversation segment becomes `memory.wiki/<id>`. URL pasted back into the chat.
Bundle	"bundle my docs about X"	AI calls `/api/bundles/ai-generate`, surfaces suggested doc ids, you confirm, returns `memory.wiki/b/<id>`.
Hub	"give me my hub URL"	AI calls `/api/user/profile`, returns `memory.wiki/hub/<you>` for paste-into-any-AI.

Why a skill rather than a plugin

A skill is plain markdown that the AI reads as instructions. No binary, no API key required (signed-out users get an anonymous capture cookie that they can claim later by signing in). Same install path works for any future MCP-compatible coding tool.

For the deeper why, see How Memory.Wiki works and MWBench for the open cross-AI verification.