Skip to main content
MuBit tracks all memory operations as a chronological activity trail. Use it for observability, debugging, compliance audit, and manual trace annotation. Activity is distinct from semantic retrieval (recall / query). It provides exact chronological ordering — what happened and when — rather than ranked relevance.

Browse activity

List recent activity entries for a run with optional type and agent filters.
# List recent activity
activity = client.control.list_activity(
    run_id="support:acme:ticket-42",
    limit=50,
    entry_types=["fact", "lesson"],
)

for entry in activity["entries"]:
    print(f"{entry['timestamp']} [{entry['type']}] {entry['content'][:80]}")

Export activity

Export the full activity trail as JSONL for offline analysis or compliance archival.
export = client.control.export_activity(
    run_id="support:acme:ticket-42",
    format="jsonl",
)
# export contains JSONL-formatted activity entries

Append activity

Manually append activity traces — useful for logging external observations, human annotations, or system events that the SDK doesn’t capture automatically.
client.control.append_activity(
    run_id="support:acme:ticket-42",
    entries=[
        {"type": "observation", "content": "Customer escalated via phone"},
        {"type": "action", "content": "Transferred to senior support"},
    ],
    agent_id="support-agent",
)

Activity vs. semantic query

listActivityrecall / query
OrderingChronological (exact timestamps)Relevance-ranked
Use caseAudit, debugging, complianceContext retrieval for LLM prompts
FiltersType, agent, time rangeSemantic similarity, entry types
OutputRaw entries as ingestedAnswer with evidence scoring
Use activity for “what happened” questions. Use query/recall for “what’s relevant” questions.

API reference

TransportEndpoint
HTTPPOST /v2/control/activity (list), POST /v2/control/activity/export (export), POST /v2/control/activities/append (append)
gRPCListActivity, ExportActivity, AppendActivity
See Control HTTP reference and Control gRPC reference for full request/response schemas.

Next steps