rohitg00/agentmemory

forget

Delete selected durable memories from agentmemory after showing them and getting explicit confirmation.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/rohitg00/agentmemory --skill forget

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.

  1. 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".

  1. On confirmation, call memory_governance_delete with memoryIds as a

comma-separated string and optional reason (default plugin skill request).

  1. 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.

  1. Lessons are separate: delete one with memory_lesson_delete and its

lessonId; memory_governance_delete does not touch lessons.

  1. 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 if memory_smart_search or memory_governance_delete is not available.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
rohitg00
コミュニティ

agentmemory-agents

How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.

1時間の導入数
1
GitHub Stars
3万
更新日
11月18日
rohitg00
コミュニティ

agentmemory-architecture

How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.

1時間の導入数
1
GitHub Stars
3万
更新日
11月18日
rohitg00
コミュニティ

agentmemory-config

Set up and diagnose local agentmemory, including MCP, environment variables, ports, and feature flags. Use when getting started, checking a connection, enabling a feature, configuring auth, or explaining why a feature is off by default.

1時間の導入数
1
GitHub Stars
3万
更新日
11月18日
rohitg00
コミュニティ

agentmemory-hooks

The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.

1時間の導入数
1
GitHub Stars
3万
更新日
11月18日