Hi there,
I’d like to suggest a small improvement to the documentation to help new developers build a clearer mental model of the Agent’s memory system.
Right now, the concept of an AgentSession (created via agent.create_session()) is introduced as a way to maintain multi-turn conversation history, but there isn’t an explicit connection drawn to the common concept of short-term memory in agent frameworks.
I think it would be helpful to add a brief note explaining:
The session object is essentially the framework’s built-in short-term memory.
It stores conversation context in memory only, tied to the session lifecycle.
It is cleared when the session ends or the application restarts.
It can also be contrasted with long-term memory (persistent storage like vector databases) to help users understand the full memory hierarchy.
This change would align the documentation with common agent design patterns, lower the learning curve, and make the framework’s design more intuitive for beginners.
Thanks for considering this suggestion!
Hi there,
I’d like to suggest a small improvement to the documentation to help new developers build a clearer mental model of the Agent’s memory system.
Right now, the concept of an AgentSession (created via agent.create_session()) is introduced as a way to maintain multi-turn conversation history, but there isn’t an explicit connection drawn to the common concept of short-term memory in agent frameworks.
I think it would be helpful to add a brief note explaining:
The session object is essentially the framework’s built-in short-term memory.
It stores conversation context in memory only, tied to the session lifecycle.
It is cleared when the session ends or the application restarts.
It can also be contrasted with long-term memory (persistent storage like vector databases) to help users understand the full memory hierarchy.
This change would align the documentation with common agent design patterns, lower the learning curve, and make the framework’s design more intuitive for beginners.
Thanks for considering this suggestion!