Echo Fade Memory

This skill turns echo-fade-memory into an installed agent memory operating layer.

The public agent contract is intentionally thin:

• store
• recall
• forget

Image memory is folded into the same store/recall/forget contract. Dashboard and debugging routes live under /v1/dashboard/* and are not part of the agent-facing tool surface.

Natural Triggers in OpenClaw

Use this skill implicitly when the conversation includes:

• remember this / 记住这个
• what did we decide before / 上次定的是什么
• user preferences, durable constraints, corrections
• project decisions worth carrying across sessions
• screenshots, diagrams, receipts, whiteboards, or UI states that may matter later
• repeated failures that reveal a reusable workaround
• elliptical continuity prompts such as 那个、这个、继续刚才的、你知道的
• time-indexed prompts such as 今天、刚刚、最近、这次、又、还、还是、依然
• continuity checks such as 你记得吗、你不是知道吗、你忘了？

Prefer over-triggering low-cost recall to under-triggering and answering as if no history exists.

If http://127.0.0.1:8080 is unreachable in a containerized environment, set:

export EFM_BASE_URL=http://host.docker.internal:8080

Quick Reference

Core Workflow

1. Recall Before Responding

Before answering about prior decisions, preferences, goals, screenshots, or unresolved issues:

./scripts/recall.sh "database choice for this project"

Inspect:

• mixed
• memories
• images
• entities

If a recalled memory is fuzzy, you can still ground it with GET /v1/memories//ground, but keep that as an internal troubleshooting path rather than the default agent contract.

2. Store Durable Facts Early

When the user says something durable, store it before moving on.

Recommended minimal memory shape:

• content
• summary
• type

./scripts/store.sh \
  "User prefers dark mode and minimal UI" \
  --summary "dark mode preference" \
  --type preference

Advanced fields still exist, but only add them when you have a clear reason:

• --importance
• --ref
• --kind
• --conflict-group

Use higher importance only for:

• preferences
• corrections
• project decisions
• constraints
• explicit "remember this" statements

3. Store Images Through the Same Entry

When the conversation includes a screenshot, whiteboard, receipt, or other durable visual artifact.

Recommended minimal image shape:

• file_path or url
• optional caption
• optional tags
• optional ocr_text

./scripts/store.sh \
  "/absolute/path/to/meeting-whiteboard.png" \
  --object-type image \
  --caption "meeting whiteboard about rollout" \
  --tag rollout \
  --ocr-text "Deployment Checklist"

Advanced image flags still exist, but they are not the default mental model:

• --session
• --kind
• --actor
• --memory-id
• --url

Use image memory when the user is likely to ask:

• "上次那张图"
• "有猫那张图"
• "包含某句话的截图"
• "和那个决定相关的图片"

4. Forget Wrong or Obsolete State

If a memory or image is incorrect, unsafe, or obsolete:

./scripts/forget.sh "that obsolete deployment note"
./scripts/forget.sh "<image-id-or-query>" image

Memory Taxonomy

Scripts

Setup

Service Availability

./scripts/health-check.sh

OpenClaw Config

Recommended entry in openclaw.json:

{
  "skills": {
    "entries": {
      "echo-fade-memory": {
        "baseUrl": "http://host.docker.internal:8080"
      }
    }
  }
}

Recommended precedence:

1. EFM_BASE_URL
2. skills.entries.echo-fade-memory.baseUrl
3. default http://127.0.0.1:8080