Checks XMemo connection status and the currently connected account/agent when the user asks whether XMemo is connected.

Save durable information for future recall; skip transient chat. Existing Projects paths attach automatically. The create_project compatibility input may create a missing project only when explicitly enabled. Use add_expense for financial records and create_memory_todo for actionable work.

Create or replace one scoped working-state record for resuming a task, next action, or blocker. Requires memory:write; it versions that state slot and refreshes its expiry without deleting other memories. Use remember for durable facts or record_event for history. Provide content or a structured state field; ttl_seconds=0 means no expiry.

Search authorized personal Knowledge Base content over published current revisions, or read one exact item/revision with bounded pagination. Requires knowledge:read.

Build a read-only, bounded context pack from multiple relevant memories. Use it when an answer needs several memory items or scoped/path-filtered context; use recall for a quick best-effort lookup or get_project_context for a whole-project snapshot. max_items/max_tokens bound output: memories that do not fit are omitted and reported, so raise max_tokens or use recall when you need the records themselves.

Read one authorized project's bounded context pack: state, TODOs, decisions, timeline, recent memories, and optional durable recall. Requires memory:read; it does not mutate project memories, and access is audit-logged. Use an exact project_id for a whole-project snapshot; otherwise use recall_context. max_items/max_tokens bound the whole pack; recent_hours affects only timeline; durable_query requires include_durable_context.

Advanced audit query. source='events' queries action/time/target audit events (for normal users prefer memory_activity); source='consolidation' inspects consolidation/lifecycle/reflection audit records (admin). Consolidates the legacy query_audit_events/query_consolidation_audit tools.

Record a significant session event, milestone, decision, or handoff note useful for reconstructing recent work. Not for durable facts/preferences (use remember).

Read authorized timeline events newest first. Requires memory:read and makes no memory changes. Use it for recent history or session resumption; use recall_context for semantic multi-memory context. limit is clamped to 1-500; session_id and event_type are exact filters.

Creates a TODO/action item in XMemo with an optional due time when the user asks to save a task, follow-up, action item, or reminder-style item to revisit at a later time.

Lists open or completed TODO/action items as a concise text answer when the user asks how many tasks, follow-ups, or saved action items are currently pending or completed; do not use it to open, browse, filter, or manage the visual TODO workspace.

Marks a TODO/action item completed when the user says a saved task is done, resolved, or no longer needed; its exact memory reference is shown by list_memory_todos.

Transition a project TODO's status. action must be one of: accept, assign, block, unblock, complete, cancel. assignee_agent_id is required for action='assign'; reason is required for action='block' (optional for cancel); note is optional for action='complete'. Consolidates the legacy accept/assign/block/unblock/complete/cancel_project_todo tools.

Transition a project decision. action must be one of: resolve, supersede, reopen. resolution is required for action='resolve'. new_context (and optionally options_json/impact_level/resolution_note) is required for action='supersede'. Consolidates the legacy resolve/supersede/reopen_project_decision tools.

Save active state, recent events, TODOs, and pending decisions for restart. Call this before handoff or when context may be lost.

Resume previous work from a saved snapshot. Call this when the user asks to resume/restart or after context loss.

Recall a few relevance-ranked memories before answering, with path/type controls and optional working-memory preference. Use it for a quick best-effort lookup; use recall_context when the answer needs a bounded multi-memory context pack.

Updates the content, location, or type of a specific saved memory when the user asks to correct, revise, move, or reclassify it. An exact reference identifies the record.

Delete one memory, TODO, or Ledger transaction by current/latest, an exact memory reference, an exact TODO ID from list_memory_todos, or an exact transaction ID from list_ledger_transactions. The default is a recoverable soft delete that restore_memory can undo; mode='hard' is permanent and unrecoverable and may be used only after the user explicitly confirms permanent deletion. Resolve ambiguous targets before deleting.

Shows aggregate statistics for all saved XMemo memories — counts by type, source, location, and optional time range when the user asks for counts, breakdowns, or distributions.

Restore a previously deleted memory. Call this only when the user explicitly asks to restore or undo a deletion.

Explains why a memory exists or matched a query whenever the user asks why something was saved there or why it was retrieved.

Read one exact authorized XMemo memory in character windows.

Use a bare memory ID (e.g. returned by recall or search) for the initial read (offset 0). The response includes 'revision' (e.g. '<memory_id>@v') and 'version'. To continue reading long content across multiple pages (when 'has_more' is True), callers MUST pass the returned 'revision' as memory_id along with 'next_offset'. This pins continuation pages to that exact snapshot and prevents torn reads if concurrent updates occur between requests. Querying with a bare memory ID always resolves to the latest active version (head), which is unpinned and subject to version tearing across updates. Embeddings are never returned.

Show version history for a memory. Call this when the user asks for previous content or changes over time.

List conflicting/inconsistent memories. Call this when the user/admin asks to review unresolved conflicts.

Resolve a listed memory conflict. Call this only when the user/admin explicitly chooses a resolution strategy.

Propose a write operation (memory, todo, profile etc.) when direct modifications are denied due to tier-gating.

Propose a todo mutation under the proposals bucket at path 'todos/{action}'.

Propose a profile mutation under the proposals bucket at path 'profile.{field}'.

Save a reusable procedure, rule, or SOP as a Cloud Skill in XMemo for future recall across connected AI agents.

Supports two usage modes (API Evolution Note: additive parameter 'url'):

1. Direct creation: Provide non-empty 'name' and 'instructions'.

2. Remote import: Provide 'url' (ClawHub slug/URL, GitHub repo/tree/raw URL, or direct HTTPS zip/markdown).

Recall reusable Cloud Skills, instructions, or sub-resources saved in XMemo. Supports Level 0 discovery by query, Level 1 root recall, and Level 2 resource recall with pinned revision_id.