---
name: setup-memento
description: Prepare or diagnose this installed Memento plugin's local runtime and model when setting it up, updating it, or resolving a runtime setup error.
---

# Set up Memento

Use this workflow when the user starts Memento's plugin setup or asks to prepare its runtime. From this installed skill's location, the plugin root is two directories above. Run the installed package's script with absolute paths:

```sh
python3 /absolute/installed-plugin/scripts/install_runtime.py --ensure
```

This prepares the Rust executable and selected local embedding model, then validates them before activation. Fresh installations use E5. Updates preserve the recorded selection and custom semantic configuration. If an older installation's choice is unknown, ask whether to keep model setup skipped or prepare E5/MiniLM, then pass the chosen `--embedding-model`. Do not infer a choice from a missing configuration file.

Show the actual setup stage and result. If Cargo, uv, permissions, network access or disk space prevent setup, explain the concrete missing condition and keep the previous runtime. Do not silently install OS tools or modify Codex hook trust. Observe tool permissions for downloads and writes; the onboarding invitation does not bypass them. Use `runtime-status` through `skills/memento/scripts/memento.py` to inspect setup without starting an installation.

Runtime preparation does not create or search for project databases. For an explicitly selected existing store, run the prepared CLI's `store-status --store /absolute/context.sqlite`; report its format and compatibility. A real store operation or `migrate` performs only supported transactional legacy migration. Never recreate a nonempty database or restore an old snapshot to solve a compatibility error.

If the user also wants checkpoint capture, explain that Codex requires review and trust of the current plugin hooks. Read `skills/memento/references/codex-hooks.md` from the plugin root, obtain an explicit repository/store/project/work scope, and configure only that scope. Do not claim runtime readiness means hooks are trusted or all project stores have been migrated.