Agent Memory (I-Pillar)
How session continuity, episodic memory, and conversation history work in the Liate framework.
The I-Pillar (Intelligence & Memory) manages persistent session states, conversational context, and long-term memory across agent runs.
Instead of losing context when an agent execution finishes, setting the I.memory parameter causes Liate to load and persist conversation turns automatically:
{
"I": {
"memory": "sessions/time-agent-india-v4"
}
}Local Flat-File Session Storage
In the open-source Liate framework, sessions are persisted locally as JSON files inside your user home directory:
~/.liate/sessions/
├── time-agent-india-v4.json
├── researcher-session-01.json
└── coding-assistant-thread.jsonEach session file stores an array of prior message exchanges, tool calls, and execution timestamps. When a new prompt is sent with the same memory ID, Liate automatically injects the prior context before running the ReAct loop.
Cloud & Sovereign Memory (pgvector)
In the Liate Cloud platform with 1-Click Supabase BYOD:
- Short-Term Memory: Stored in Supabase
liate_sessionstable with sub-millisecond retrieval. - Long-Term Semantic Memory: Vector embeddings stored with PostgreSQL
pgvectorfor semantic similarity search over months of past agent history.
