Problem
When recalling memories, custom metadata fields stored via store_memory are not returned in any response format (text, items, detailed, or json). This makes metadata effectively write-only — you can store it but never see it.
Currently, detailed recall returns:
- ID, Type, Created timestamp, Importance, Confidence, Tags, Score, Match reason
What's missing:
- ❌ Custom metadata fields (e.g.
created_by, model, task, topic)
- ❌
updated_at / last_accessed
- ❌ Any indication that metadata was stored at all
Why It Matters
As multi-agent setups grow (multiple agents writing to the same memory graph), provenance becomes critical. Knowing which agent or which model stored a memory is important for auditing, debugging, and trust scoring. But that's only useful if the data surfaces on recall.
This also blocks any future consolidation work that wants to preserve source_agents[] arrays or merge provenance across memories.
Proposed Fix
Surface a metadata block in recall responses — at minimum in detailed and json formats. Example:
{
"id": "abc123",
"type": "Decision",
"content": "...",
"importance": 0.9,
"tags": ["autohub", "2026-03"],
"metadata": {
"created_by": "hub-developer",
"model": "claude-sonnet-4.6",
"task": "PR review automation",
"topic": "AutoHub architecture"
},
"created_at": "2026-03-05T...",
"updated_at": "2026-03-05T..."
}updated_at and last_accessed should also be included while we're at it.
Acceptance Criteria
Problem
When recalling memories, custom
metadatafields stored viastore_memoryare not returned in any response format (text,items,detailed, orjson). This makes metadata effectively write-only — you can store it but never see it.Currently,
detailedrecall returns:What's missing:
created_by,model,task,topic)updated_at/last_accessedWhy It Matters
As multi-agent setups grow (multiple agents writing to the same memory graph), provenance becomes critical. Knowing which agent or which model stored a memory is important for auditing, debugging, and trust scoring. But that's only useful if the data surfaces on recall.
This also blocks any future consolidation work that wants to preserve
source_agents[]arrays or merge provenance across memories.Proposed Fix
Surface a
metadatablock in recall responses — at minimum indetailedandjsonformats. Example:{ "id": "abc123", "type": "Decision", "content": "...", "importance": 0.9, "tags": ["autohub", "2026-03"], "metadata": { "created_by": "hub-developer", "model": "claude-sonnet-4.6", "task": "PR review automation", "topic": "AutoHub architecture" }, "created_at": "2026-03-05T...", "updated_at": "2026-03-05T..." }updated_atandlast_accessedshould also be included while we're at it.Acceptance Criteria
detailedformat returns fullmetadataobjectjsonformat returns fullmetadataobjectupdated_atandlast_accessedtimestamps included in responses{}or omit the field)