Yaps Memory

View saved version →

---
name: yaps-memory
description: Use the user's private local Markdown Yaps vault as a durable memory store across AI tasks. Trigger for cross-task memory, remembered facts, personal knowledge, prior context, or requests to remember, capture, retrieve, search, cite, organize, update, tag, connect, or recover notes, ideas, dictation history, meeting notes, resources, and daily notes stored in Yaps.
---

# Yaps Memory

Use Yaps as a private, file-backed memory layer shared between the user and the current AI client.

## Choose the available transport

Test capabilities instead of guessing the host from its product name or user agent:

1. Prefer Yaps MCP tools such as `vault_search` and `vault_note_get` when they are available. MCP enforces Yaps Agent Access and supplies the most structured interface.
2. If MCP is unavailable, try the skills-only CLI fallback with `vault status`.
   On macOS or Linux, locate `yaps-plugin-launcher.sh` at
   `<skill-dir>/scripts/yaps-plugin-launcher.sh`; for a full local plugin
   checkout, fall back to `<plugin-root>/scripts/yaps-plugin-launcher.sh`.
   This launcher can use Codex Desktop's bundled runtime on a clean computer
   where `node` is not installed globally. On Windows, locate the adjacent
   `yaps-plugin-launcher.cmd` instead; for a full local plugin checkout, fall
   back to `<plugin-root>/scripts/yaps-plugin-launcher.cmd`.
3. Run the fallback on macOS or Linux as:

   ```text
   sh <launcher> --action vault.status --stage reachability -- yaps --pretty vault status
   ```

   In Windows PowerShell, run:

   ```text
   & "<launcher.cmd>" --action vault.status --stage reachability -- yaps --pretty vault status
   ```

   The runner honors an explicit override, checks `PATH`, then finds the CLI
   packaged inside the installed Yaps app, and validates it with a bounded,
   read-only `status` command. Never ask the user to install a CLI, edit PATH,
   copy a token, or configure MCP.
4. If either transport succeeds, continue with it for the task. Do not stop merely because MCP is absent; public uploaded plugins may intentionally be skills-only.
5. If the CLI validates but MCP is unavailable, say that the CLI is working and
   the private-vault connector is unavailable; continue through the CLI fallback
   when the task permits it. Never call that state “CLI missing.” If neither
   transport can reach Yaps, repeat the runner's specific recovery guidance. If
   the current task cannot reach the local engine, direct the user to a
   local-capable session on the computer where Yaps is installed: in Claude,
   that is Claude Code or the Claude desktop app; if the task is ChatGPT web,
   browser-only, or cloud-hosted, offer
   [ChatGPT desktop](https://chatgpt.com/download/) and a new local-capable Work
   or Codex task. Do not claim Yaps is uninstalled merely because it was not
   found in the known locations.
   When its recovery code is `cli_missing`, offer
   [Yaps desktop](https://yaps.ai/download) as the direct install-or-open step;
   do not describe it as a separate CLI download.

The plugin, Yaps desktop installation, sign-in, and trial or Yaps Pro activation may happen in any order. Account or subscription changes do not require reinstalling or reconnecting the plugin. A new task is only needed when the current task began before the local Yaps capability became available.

## Private operational diagnostics

Run every local Yaps CLI command through the platform launcher and runner. Use a stable content-free action and one of these stages: `reachability`, `authentication`, `readiness`, `execution`, or `export`. macOS/Linux examples:

```text
sh <launcher> --action vault.search --stage execution -- yaps --pretty vault search-semantic "<query>" --limit 8
sh <launcher> --action vault.get --stage execution -- yaps --pretty vault get "<relative-path>"
```

On Windows, use `& "<launcher.cmd>"` in place of `sh <launcher>`. If the launcher or runner is unavailable but the CLI itself is reachabl

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.