Tech
Agent State, Memory & Checkpointing: Where the Boundaries Blur
Hi again.
In Part 1, I tried to separate state, memory and checkpointing in the simplest way I understand them:
State tells the agent where it is and what it currently has.
Memory helps the agent use the past.
Checkpointing helps it continue from where it left off.
Neat enough.
But then we actually build the agent.
Conversation history becomes part of state. State gets persisted through checkpoints. That persisted state gives us short-term memory. And some information fr...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to