EXAMPLES.md
# forget worked examples
## Delete a selected durable memory
User: "Forget that note where I pasted the API key."
```json
memory_smart_search { "query": "api key", "targetLayer": "memory", "project": "app", "limit": 20 }
```
Show the returned memory ID and title without displaying the secret value:
> Found memory `abc12345` in project `app`: "Staging API configuration".
> Delete this memory?
After explicit confirmation:
```json
memory_governance_delete { "memoryIds": "abc12345", "reason": "user privacy request" }
```
If the response reports `deleted: 1`, report one deletion. If it reports
`deleted: 0` and `notFound: ["abc12345"]`, report that the memory was not found.
For mixed results, state the actual count and any failed or missing IDs.
## A request to erase a whole session
User: "Delete everything from the throwaway spike session."
Explain that this tool deletes selected durable memories only. A relevance
search limited to 20 results cannot enumerate all session data, and observation
IDs are not accepted as durable-memory IDs. Do not claim complete erasure.
Offer a review of matching durable memories with the scope clearly stated.
Lessons have a separate `memory_lesson_delete` operation.
## User declines
User: "Actually, keep them."
Do not call delete. Report that nothing was deleted.
SKILL.md
---
name: forget
description: Delete selected durable memories from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.
argument-hint: "[what to forget - session ID, file path, or search term]"
user-invocable: true
---
The user wants to remove data from agentmemory: $ARGUMENTS
## Quick start
```json
memory_smart_search { "query": "old api key in config", "targetLayer": "memory", "limit": 20 }
```
Show the matches, get a yes, then:
```json
memory_governance_delete { "memoryIds": "abc12345,def67890", "reason": "user privacy request" }
```
Expected output:
```text
Found 2 matching memories. Confirmed. Deleted 2 memories.
```
## Why
This is destructive and irreversible. Show exactly what will be deleted and get
an explicit yes before calling delete. Delete by memory ID, never a bare session.
## Workflow
1. Search with `memory_smart_search`, the user's text as `query`,
`targetLayer: "memory"`, `limit: 20`, and the requested project/agent scope.
These are selected relevance matches, not an exhaustive inventory.
2. Show what matched: memory ids, titles, and scope. Redact secret values. Ask for explicit
confirmation. Do not proceed on silence or a vague "sure, whatever".
3. On confirmation, call `memory_governance_delete` with `memoryIds` as a
comma-separated string and optional `reason` (default `plugin skill request`).
4. Observation or whole-session erasure is not supported by this operation.
Explain that limit before proceeding; never label selected memory deletion
as a complete session wipe. Do not pass observation IDs or a `sessionId`.
5. Lessons are separate: delete one with `memory_lesson_delete` and its
`lessonId`; `memory_governance_delete` does not touch lessons.
6. Check `deleted`, `notFound`, and `failed` in the response. Report actual
deletions and unresolved IDs separately. Recheck the selected IDs before
retrying a failed request; an interrupted response may hide a completed write.
## Anti-patterns
WRONG: search returns matches, you immediately call `memory_governance_delete`
without showing them or waiting for a yes.
RIGHT: list the matches, ask "Delete these 2? (yes/no)", and only delete after
an explicit yes.
## Checklist
- Matches were shown to the user before any delete.
- An explicit yes was received, not assumed.
- `memoryIds` holds real ids from the search, never a bare `sessionId`.
- Final message states the actual count deleted.
## See also
- `remember`: the write side; forget is its undo.
- `recall`: find the exact memory id before deleting.
## Troubleshooting
See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) if `memory_smart_search` or `memory_governance_delete` is not available.
TROUBLESHOOTING.md
<!-- AUTOGEN:troubleshooting START - generated by scripts/skills/generate.ts, do not edit by hand -->
# Troubleshooting agentmemory skills
Recovery steps for separately installed skills. This document is generated into
each skill directory so native skill readers can open it without parent traversal.
## "MCP tool not available"
Missing tools can mean a stopped MCP process, a disconnected daemon, or an
explicitly reduced tool surface. Walk these in order:
1. Identify the host. In Claude Code, inspect `/plugin list` and `/mcp`.
In Hermes, inspect the configured memory provider and `mcp_servers` separately.
In OpenClaw, validate the host configuration and inspect its MCP servers and
native plugins separately. In Pi or OMP, inspect `/agentmemory-status` and the
MCP inventory separately; native save/search does not prove the broader tools
are connected. Do not run another host's setup commands.
2. Restart or reload the affected host connection after configuration changes.
3. Inspect the connected tool inventory. Hermes may namespace MCP tools; invoke
the actual advertised names and schemas. A native memory provider is not
proof that every MCP tool or shared skill is available.
4. Check `agentmemory status` and the daemon's `AGENTMEMORY_TOOLS` setting.
Codex's bundled bridge lists the daemon's enabled tools. The standalone shim
used by other hosts can fall back to seven basic tools with a separate store.
Do not claim full daemon functionality based on those seven tools.
5. If `agentmemory connect codex` and the Codex plugin are both enabled, choose
one MCP connection. Check `/hooks` before adding global hook fallbacks.
Hermes, OpenClaw, Pi and OMP connector installations bundle skills; other hosts
may install them separately. Check the host's skill inventory and open this file
from the installed skill directory. Test automatic capture with a real turn and
a recorded observation; tool connectivity alone does not establish lifecycle
capture.
An outage or timeout is not an empty search result. Report the failure. A write
may have committed before the response was lost; inspect state before retrying.
## REST fallback
When the MCP tools stay unavailable but the daemon is running, call the REST
API directly:
1. Set `AGENTMEMORY_URL` to the daemon base URL (default `http://localhost:3111`).
2. The REST API requires a bearer credential by default. Use the host's explicit
`AGENTMEMORY_SECRET`; for loopback URLs only, fall back to the secret in
`~/.agentmemory/.env` and then `~/.agentmemory/secret`. Load the value locally
without displaying it. Never send a local-file secret to a remote URL.
If `AGENTMEMORY_CREDENTIAL_MODE=explicit`, require the explicit host credential
and do not read local credential files.
Authenticated REST fallback requests require HTTPS for non-loopback
URLs; HTTP is allowed for loopback URLs (`localhost`, `127.0.0.0/8`, or `[::1]`).
Reject redirects on authenticated requests. Do not print or save the secret.
Endpoint map by skill:
| Skill | REST call |
| --------------- | --------------------------------------------------------------- |
| remember | `POST /agentmemory/remember` |
| recall | `POST /agentmemory/smart-search` |
| recap | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search` |
| handoff | `GET /agentmemory/sessions` + `POST /agentmemory/smart-search` |
| session-history | `GET /agentmemory/sessions` |
| commit-context | `GET /agentmemory/session/by-commit?sha=<sha>` |
| commit-history | `GET /agentmemory/commits` (URL-encode every query param) |
The MCP host reads the plugin MCP configuration. Restart the daemon after
changing its configuration, then restart or reconnect the host MCP process after
changing its URL or explicit secret. The local bridge reads the credential files
for each request; it does not inherit other daemon `.env` settings.
<!-- AUTOGEN:troubleshooting END -->