Persist a long-term memory for the current user.

When to use:

• The user states a preference, decision, fact, plan, or goal that should outlive this chat.

• You learn a stable property of the user, their project, or their tooling.

• The user explicitly says "remember", "记住", "save this".

When NOT to use:

• Ephemeral chat turns ("ok", "thanks").

• Sensitive secrets (API keys, passwords) — refuse and warn the user.

• Information you can re-derive from the codebase on demand.

Returns: { id, created_at, schema_version, embedding_status } — use memory_get for the full record.

Hybrid semantic + keyword search over the user's memories.

When to use:

• The user asks "do you remember…" or "what did I say about X".

• Before answering project-specific questions, search for stored preferences and decisions.

• You need to ground your answer in user-supplied facts.

When NOT to use:

• You already have the memory id → use memory_get.

• You just want the most recent items in a namespace → use memory_recall.

Returns: ranked list of MemoryRecord with a raw RRF relevance score (typically 0.01–0.04).

Replay recent or important memories from a namespace, without a query.

When to use:

• At the start of a new chat — to load recent context.

• The user says "what have we been working on" / "remind me".

• You want a chronological feed rather than a search match.

When NOT to use:

• The user has a specific question → use memory_search.

• You already have the id → use memory_get.

Fetch a single memory by id.

When to use:

• You already have a memory id from a previous memory_search / memory_recall / memory_save call.

• The user references "that memory you saved" and you stored the id.

When NOT to use:

• You only have a vague query — use memory_search or memory_recall instead.

Patch an existing memory. Only the fields you provide are changed.

When to use:

• The user corrects a previously stored fact ("actually, I use Tailwind v4 not v3").

• You need to add tags / entities to an existing memory.

• The user lowers/raises priority of a memory.

When NOT to use:

• The memory is wrong AND no longer relevant → use memory_delete.

• You don't have the id yet → search first.

Delete a memory. Defaults to a soft delete (30-day recovery window).

When to use:

• The user explicitly asks to forget something ("forget that I said …").

• A memory is clearly wrong AND not worth correcting.

• GDPR / privacy removal request.

When NOT to use:

• The memory is just outdated — prefer memory_update.

• You're unsure — ask the user first.

Note: deletes are always soft — the API has no immediate hard delete. Soft-deleted memories are purged permanently after the 30-day window.

List all namespaces the current user has, with per-namespace counts.

When to use:

• Before deciding which namespace to save to, when the user has multiple projects.

• To answer "what projects do I have memories for?".

• For diagnostics.

Returns: array of { name, created_at }.

Probe the Kireo service and report local + remote health.

When to use:

• User reports "memory tools aren't working".

• You hit unexplained errors and need to confirm the API is reachable.

• First-time setup verification.

Returns: { local: { server_version, node_version, platform }, remote: { status } }.