tex.conversations.remember to store new conversation turns. This is the write side of the loop from the Quickstart.
Parameters
list[dict]
required
List of turn dicts. At least one turn is required. Empty lists return
422. Each turn:str
required
The conversation, channel, or task this batch belongs to.
dict | None
Free-form metadata attached to the batch. Deep mode can use it during search.
Returns
str | None
Stable identifier for this write. Use it to match SDK logs with server logs.
list[str]
IDs of the active-memory fragments. These are recallable right away.
str | None
Reserved for future async passive job tracking. Currently always
null.Usage | None
tokens_in / tokens_out for this call. tokens_out is typically 0 on remember. Always present in production.Examples
Single user turn
Both sides of a turn
Backfill historical conversation
Pre-extracted observations
If your app already extracted structured facts, pass them inline:Behavior
1
Active write
The call returns after active memory is saved, usually around 150ms. The turn is recallable right away.
2
Background enrichment
Tex extracts observations and entities in the background. They appear in later recalls.
Best practices
- Batch. Pass dozens of turns in one call. Don’t loop one-per-turn.
- Use UTC ISO 8601 for timestamps (
...Zsuffix). This keeps temporal queries clear. - Skip system messages. They consume tokens and add noise to recall.
- Run
rememberoff the request path. Use Celery, RQ, or aBackgroundTasksqueue when users should not wait.
Idempotency
Tex computes a stable hash per turn from text, timestamp, and role. Re-sending the same turn is a no-op. It does not create duplicate active memory or double bill the same turn. This makes retries safe after a network blip.Next: Recall
Pull the relevant slice of memory.

