Memory layers
The
conversation_memory tool gives the model an explicit way to request durable memory when the current prompt is insufficient. Memory access travels through the internal gateway API and remains scoped to the organization and conversation.
Context budget
IncreasingCHAT_HISTORY_LIMIT can improve continuity but increases latency, token usage, and privacy exposure. Prefer concise summaries and structured contact facts over sending a long raw transcript on every turn.
Knowledge and memory have different authority. Knowledge represents approved tenant content; conversation memory represents what participants said and may be incomplete or unverified.
Privacy guidance
- Avoid storing secrets, full payment data, or authentication codes in memory.
- OTP values are redacted from agent logging and should not be copied into summaries.
- Apply retention policy to messages, agent runs, and observability events.
- Restrict internal memory endpoints with
AI_TOOL_SECRETand private networking. - Include organization context in every memory lookup and cache key.