Skip to main content
Mneno tracing records why memory operations made specific decisions. Traces are local, in-memory, deterministic, and disabled by default. Core tracing does not use OpenTelemetry, external services, telemetry uploads, or network calls.

Enable tracing

Search keeps its existing list[MemorySearchResult] return type. Use client.last_trace_id to inspect its latest trace. Result models such as ContextPackage, CompactionDiff, ExtractionResult, HierarchyEvaluationResult, and Timeline include a trace_id when tracing is enabled.

Inspect events

Trace events cover operations such as:
  • candidate filtering and score calculation
  • semantic retrieval, reranking, and session boosts
  • per-candidate score components, final rank, and inclusion or exclusion reasons
  • internal memory IDs plus source, dataset, LOCOMO, and original IDs when present in memory metadata
  • context inclusion, exclusion, deduplication, and budget exhaustion
  • compaction decisions and storage mutations
  • conflict reports, resolutions, and audit additions
  • hierarchy retention scores and transitions
  • extraction mode and validation errors
  • session changes, continuity, and timeline ordering

Use TraceInspector

You can filter by event_type, memory_id, or session_id.

Export traces

Single-trace exports use a stable versioned envelope:
Structured fields with credential-related names are redacted before recording. Do not place raw provider payloads or secrets in trace messages.

Clear local traces

Clearing traces does not alter stored memories.