session_id and user_id. When you make a request with the same identifiers, the agent automatically includes relevant conversation history in the context, enabling it to reference previous messages and maintain continuity.
Session vs User IDs:
session_id- Isolates conversation threads. Each session maintains separate context.user_id- Groups conversations by user. Useful for maintaining user-specific context across sessions.
You cannot define
session_id alone. Use user_id for long-term memory (persists across sessions) or both session_id and user_id together for short-term memory (isolated to a specific session).Supported Memory Backends
Hypertic supports multiple memory backends. Click on a backend to see setup and usage examples:InMemory
UseInMemory for testing and development. Data is stored in RAM and lost when the process ends:
For production applications, use persistent storage like PostgreSQL or MongoDB. See the individual backend pages for setup instructions.