Problem
The current default prompts suggest tagging memories with project name and date, but don't mention metadata at all. This means agents store memories with almost no provenance — you can't tell which agent created a memory, what model was used, what task it was part of, or what the conversation was about.
In single-agent setups this is fine. In multi-agent setups (multiple agents writing to the same memory graph), this becomes a real problem for auditing, debugging, and trust.
Proposed Change
Update any default prompts, system prompt snippets, or documentation that describes memory structure to also recommend a standard metadata block on store_memory calls.
Suggested metadata fields (cheap to store, high value):
| Field |
Example |
Notes |
created_by |
"hub-developer" |
Agent name/ID that stored the memory |
model |
"claude-sonnet-4.6" |
Model used at time of storage |
task |
"PR review automation" |
Task or job the agent was performing |
topic |
"AutoHub architecture" |
Conversation or research topic |
session_id |
"agent-abc123" |
Task/session ID for traceability |
source |
"slack" / "whatsapp" / "code" |
Where the memory originated |
confidence |
0.85 |
Already supported — make sure it's in the prompt |
Metadata is cheap. The cost of over-storing provenance is negligible vs. the value of being able to audit memory origins later.
Why metadata over tags?
Tags are hard filters — adding hub-developer as a tag means queries filtering on other tags will miss those memories. Metadata is additive and doesn't affect semantic search or tag-based filtering. Provenance belongs in metadata, not tags.
Acceptance Criteria
Related
- verygoodplugins/automem: Return metadata fields in recall responses by default
- verygoodplugins/automem: End-to-end metadata audit
Problem
The current default prompts suggest tagging memories with project name and date, but don't mention
metadataat all. This means agents store memories with almost no provenance — you can't tell which agent created a memory, what model was used, what task it was part of, or what the conversation was about.In single-agent setups this is fine. In multi-agent setups (multiple agents writing to the same memory graph), this becomes a real problem for auditing, debugging, and trust.
Proposed Change
Update any default prompts, system prompt snippets, or documentation that describes memory structure to also recommend a standard
metadatablock onstore_memorycalls.Suggested metadata fields (cheap to store, high value):
created_by"hub-developer"model"claude-sonnet-4.6"task"PR review automation"topic"AutoHub architecture"session_id"agent-abc123"source"slack"/"whatsapp"/"code"confidence0.85Metadata is cheap. The cost of over-storing provenance is negligible vs. the value of being able to audit memory origins later.
Why metadata over tags?
Tags are hard filters — adding
hub-developeras a tag means queries filtering on other tags will miss those memories. Metadata is additive and doesn't affect semantic search or tag-based filtering. Provenance belongs in metadata, not tags.Acceptance Criteria
store_memoryprompt examples include ametadatablocksource_agentsshould be a union array (not overwritten) — flag this as a known limitation until automem consolidation supports itRelated