Kemory

L1 — Return every active memory in a namespace as raw dicts, no truncation, no compression. Requires memory:read permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_get_raw

Get contextual memories relevant to a conversation or topic. Searches across all accessible namespaces (or a specific namespace) and returns the most relevant memories, optionally synthesised by the AI backend. Requires memory:read permission. HOW YOU PHRASE THE TOPIC CHANGES WHAT YOU GET BACK. Retrieval compares it against each memory's own wording, so name the topic in the vocabulary the notes were written in — services, config keys, identifiers — rather than describing it conversationally. If the result looks thin, try a second phrasing before concluding nothing relevant is stored. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_get_context

Get an optimized, prompt-ready context block for one namespace session. This keeps the latest raw user/assistant exchanges readable and folds older exchanges into a rolling token-budgeted digest. Namespace and session summaries are included as long-term background orientation; the digest itself is grounded only in prior digest + source exchanges. AAAK is never returned here because AAAK is byte-oriented storage/export compression, not the default LLM-context representation. Append the current user message after this tool output. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_get_session_context

Get a cross-namespace memory overview for the user. Ideal for session-start context injection — gives the agent a single block covering all of the user's memory namespaces. depth='l3' (default): returns per-namespace L3/L3.1 summaries already computed by the compression pipeline — fast, no LLM call. depth='l4': adds one LLM synthesis pass across all namespace summaries via core-ai-backend — richer but slower; synthesis=null if backend is unavailable. Optional 'namespaces' list restricts which namespaces are included. Freshness: summaries are built asynchronously and can lag recent writes. Each namespace item carries summary_as_of (when its summary was generated) and memories_since_summary (memories written after that) — when memories_since_summary is high, prefer kemory_recall_memory / kemory_get_context for the latest facts. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_get_user_context

Return the user's PERSISTED profile — 'static' (stable preferences) and 'dynamic' (recent activity) halves, served from a stored row in one lookup with no LLM call; the row rebuilds lazily when stale. Use section to fetch one half, refresh=true to force a rebuild. Requires memory:read permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_get_profile

List all namespaces in the user's S9N Memory Vault with memory counts. Useful for discovering available data before searching. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_list_namespaces

List the user's projects with their namespace mapping and memory counts. Explicit projects (created aliases spanning 1+ namespaces) merge with implicit ones (bare project:* namespaces). Pass a returned project name to kemory_memory / kemory_recall via their 'project' argument for project-scoped writes and reads. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_list_projects

List all stored agent skills — learned procedures with name, trigger, and steps. Requires memory:read permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_list_skills

Promote a transient chunk (E09 multi-modal pipeline) so the CogOS retire pass leaves it alive. Use BEFORE referencing a transient memory from a skill or memory that won't carry a cited_memory_id, or as an explicit pin when you know an artifact is load-bearing. Idempotent — promoting an already-promoted memory is a no-op. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_promote_memory

Search memories, optionally returning the user profile in the same call (include_profile=true appends a fast L3 cross-namespace overview). Friendly alias of kemory_recall_memory — identical ranking and envelope. Requires memory:read permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_recall

Search and retrieve memories from the user's S9N Memory Vault. Supports text search, namespace filtering, content type filtering, and pagination. Requires memory:read permission. HOW TO SEARCH WELL. Retrieval matches your query against the wording the memory was STORED in, so a query in your own words often misses a memory that is genuinely there. Measured: recall drops from roughly 2-in-3 to 1-in-5 when the query paraphrases instead of reusing the original phrasing. 1. Use the domain's own vocabulary — the identifiers, product names, error strings and jargon the note would have been written with (e.g. 'S9N-5680 DEK rotation', not 'how we handle encryption keys'). 2. If the first search returns nothing useful, SEARCH AGAIN with different phrasing rather than concluding the memory does not exist. Two or three phrasings cost one round-trip each and materially change what comes back. 3. Prefer specific nouns over descriptions of intent. 'HPA autoscaling threshold' beats 'what did we decide about scaling'. 4. Results are ranked, not filtered for truth — a low-relevance hit may be returned simply because it was the closest available. Judge the content, not its position. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_recall_memory

Resolve a contradiction between two memories: the loser is soft-superseded (bi-temporal invalid_at + superseded_by marker, same mechanics as the automatic contradiction judge), a conflict_resolved provenance event is recorded, and a 'supersedes' relation edge is written. Idempotent — resolving an already-resolved pair changes nothing. Requires memory:delete permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_resolve_conflict

Save one memory. Friendly alias of kemory_store_memory: same storage path, same dedup/enrichment, but namespace is optional and defaults to 'shared'. Requires memory:write permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_memory

Store a new memory in the user's S9N Memory Vault. The memory is associated with a namespace and can include metadata, content type, and an optional TTL. Requires memory:write permission. HOW TO WRITE A RETRIEVABLE MEMORY. Retrieval matches a future query against the wording you store now, and future queries are usually phrased as questions in the user's own words — not in the jargon of the moment. Write for that. 1. Open with a line phrased the way someone would later ASK for this (e.g. 'How many times does the provider call retry before giving up?'), then give the answer and the detail. 2. Keep the identifiers, error strings and product names in the body — they are what makes exact lookup work, and they are lost if you only write a summary. 3. Include the plain-language terms alongside the jargon, not instead of it. Both phrasings in one memory beats either alone. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_store_memory

Store a learned skill (procedural memory) with name, trigger, and ordered steps. Requires memory:write permission. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_store_skill

Return the calling identity as Kemory sees it: user id, agent registry entry (when agent-authenticated), and organisation scope. Use to verify which tenant and agent a session is bound to before writing. Scope: memories are isolated per-organisation and per-user. You cannot read or write outside your org, and (by default) you cannot see other users' private memories within your org. Use the visibility option (private/team/org) to share with teammates.

kemory_whoami