← Mnemoverse MemoryCONTENT HISTORY

Update to Mnemoverse Memory

Snapshot Nov 7, 2026 · 00:09 UTC · version 1.0.6

Collection source: downloaded plugin package.

WHAT CHANGED

Supporting file metadata differs

Supporting file metadata differs

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Save Mnemoverse Memory and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Supporting files

Before

Nov 6, 2026 · 18:19 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":241}]

After

Nov 7, 2026 · 00:09 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":432}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

No SKILL.md text changes between these observations.

Full technical diff · 1 changed fields

changed /included_files

BEFORE
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 241
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 432
  }
]
Full snapshot data
{
  "description": "Save a concise project brief in Mnemoverse so the user can resume in another connected AI tool. Use when asked to remember project context, prepare a memory handoff or save a brief; ordinary summaries do not require saving.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 432
    }
  ],
  "name": "project-brief",
  "skill_md_contents": "---\nname: project-brief\ndescription: \"Save a concise project brief in Mnemoverse so the user can resume in another connected AI tool. Use when asked to remember project context, prepare a memory handoff or save a brief; ordinary summaries do not require saving.\"\n---\n\n# Continue a project in another AI tool\n\nThe user's request defines what to save. A project handoff carries selected useful context, not their entire conversation, files or automatically discovered private information.\n\n## Prepare the brief\n\n- Start with the project facts already supplied in this conversation or the documents the user selected. If a new account has no context, ask for the project name and what the next assistant needs to know in one short question. Do not create a fictional sample project or a placeholder memory.\n- Include the goal, confirmed decisions and constraints, relevant current status and next step when supplied. Distinguish decisions from suggestions and date status that can change. Keep only details needed to continue the project. Do not invent missing sections to fill a template.\n- If the user supplies an exact personal project domain, use it as given without `memory_stats`; that label does not need to exist before the write. Use `memory_stats` only when choosing or disambiguating an existing project domain. Use `memory_read` for relevant earlier project context when needed; do not enumerate all personal memories. A domain is a label on records, not a separately created empty project. For a clearly named new project, choose a simple domain such as `project:<project-name>` on the first real write.\n- If existing notes contradict the current account, keep the disagreement visible and resolve any ambiguity that would change the brief. A new write does not edit or remove an earlier note.\n\n## Save and hand off\n\n1. Save the brief with `memory_write` in the chosen personal project domain, using self-contained statements and a few relevant `concepts`. Independent decisions can be separate notes. Include sources for material facts when known. A request to use another AI under the same account does not authorize putting the brief in a shared room.\n2. Report only notes whose result says `stored: true`. For `stored: false`, report the returned reason if present and distinguish already known content from new facts that were not saved. Do not retry the same fact with cosmetic rewording. If the result is unreadable, state that the save is unconfirmed.\n3. Give a short handoff prompt containing the project name and exact domain, for example: “Read my Mnemoverse notes in project:<actual-name> and help me continue from the saved next step.” Use the actual saved scope, never the example placeholder.\n4. Explain that the other AI tool must support Mnemoverse and be connected separately to the same Mnemoverse account. It can retrieve the saved brief; this does not transfer the whole chat, modify that tool's built-in memory or prove the other tool has already read it.\n\nDo not include passwords, API keys, payment data, MFA codes, government IDs or health records. If Mnemoverse tools are unavailable, show the concise unsaved brief and explain the connection step without claiming it is in memory. In ChatGPT, point to https://mnemoverse.com/docs/api/chatgpt; use https://mnemoverse.com/docs/api/install-by-host for another host. Never request credentials in the conversation.\n"
}

SHA-256 of public snapshot: e391db0a0daebb5cfb34df77faf58e1352f0d250ffd91359049528b128cc9ff7