Repository navigation
v0.5.1 (experimental)
Record labels now hold up on memory servers that resolve references from recent messages and overlay updates, such as Mem0 (#41). Thanks to Edward Izgorodin for the analysis of Mem0's message buffer.
@adtl/labels
- Record stamps are written under a key per session,
adtl/record-label/<session>, and stamp keys the agent supplies are dropped. On servers that lay an update's metadata over the stored metadata (Mem0), a clean session's update no longer replaces a tainted stamp. Stamps written by 0.5.0 under the singleadtl/record-labelkey are still read. - Tool rule
scopeInto(e.g.run_id): a tainted session's writes get a scope id named after its label, so servers that resolve references from recent messages of the same scope (Mem0) don't build a clean session's facts from a tainted session's text. Clean sessions can't name a tainted scope.scopeRecord().
@adtl/interceptors
adtl.labelappliesscopeIntoon the request phase oftools/call, alongsidelabelInto.
@adtl/gateway
- Docs: which Mem0 paths carry record labels and which need a strict rule (
history(), andlist_events/get_event_statuson Mem0's hosted MCP server).
Examples
examples/fake-memorykeeps Mem0's 10-message buffer per scope, resolves "the same place as before" from it, and hasget_memoryandupdate_memory(metadata overlaid).