tex.recall before you call your model. It returns the memory that best matches the current user message.
For mode, top_k, and confidence, read Recall and ranking. This page lists the Python fields.
Call recall directly on the client:
tex.recall(...). There is no tex.recall.search(...).Parameters
Natural-language query. The user’s latest message usually works well.
Session to search. Use the same
session_id you wrote with.Retrieval depth. See Recall and ranking.
Number of hits across all kinds. Defaults to 15 in
active mode and 25 in deep mode. The server caps the final value at 30.When true, the response includes a pre-rendered
timeline string (not a structured list).Returns
Raw conversation turns most relevant to
q.Small facts extracted from past turns, such as preferences or decisions.
People, places, and things linked across observations.
Calibrated confidence in [0, 1]. Higher means the returned memory is more likely to help.
A pre-rendered chronological summary of the relevant events. Set only when
include_timeline=True.Echoes the request mode.
tokens_in / tokens_out billed for this call. Always present in production.RecallHit fields (turns / observations)
RecallEntity fields (entities only)
RecallEntity is not the same as RecallHit. It has label instead of text, and it does not have kind or timestamp.
Examples
Build a chatbot system prompt
Confidence-gated fallback
Temporal queries
timeline is a free-form string. Drop it into a prompt as text. Do not treat it like an array.
Multi-source recall
If you have both a long-lived user “bio” and a per-conversation session, query both:Performance
| Mode | Typical p50 | p99 | When to use |
|---|---|---|---|
active | 1.7s | 2.5s | Every interactive call |
deep | 3.5s | 6s | Periodic analysis, low-confidence retries |
timeout=2.0 on the constructor for interactive paths. Catch APITimeoutError and continue without memory:
Next: Track usage
Read your token totals.

