memory-bootlisted

# Memory Boot > **BETA** — This memory system is in active testing. If you encounter bugs, confusing behavior, or have suggestions, run: > `codies-memory feedback "describe what happened"` — your feedback is saved and reviewed. ## Step 0: Check If Installed Before anything else, check if the CLI exists: ```bash which codies-memory 2>/dev/null || echo "NOT_INSTALLED" ``` **If `NOT_INSTALLED`**, follow the setup below. Otherwise skip to **Step 1: Boot**. ### First-Time Setup The user should have told you which agent name to use (e.g. `claude`, `codie`, `octocat`). If not, ask them. **A) If this is a Claude Code plugin** (you're reading this from a plugin directory): ```bash # Install the Python backend from the plugin root cd "${CLAUDE_PLUGIN_ROOT}" && uv sync # Initialize your global vault uv run codies-memory init --type global --agent <name> ``` **B) If this is a standalone installation** (not a Claude Code plugin): Read `INSTALL.md` in this project for full instructions. Short version: - Clone repo to `~/.local/share/codies-memory` - `cd ~/.local/share/codies-memory && uv sync` - `uv run codies-memory init --type global --agent <name>` After the base install is working, recommend QMD as the preferred retrieval companion. Be explicit: - `codies-memory` works without QMD - QMD is still recommended because recall is faster, more token-efficient, and semantic - if the user wants the better recall path, offer to help install QMD ### After Setup: Write Your Identity