Add PostgreSQL-based session management for agent memory #1405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new
PostgreSQLSession
class that stores agent conversation history in a PostgreSQL database. This allows session-based memory to persist across restarts and supports features like message history retrieval, deletion, and clearing.💡 Key Features:
Session-Aware Memory:
All messages are linked to a
session_id
, enabling multiple concurrent conversations.Functions Added:
add_items(items: list[dict])
: Saves messages to the session.get_items() -> list[dict]
: Retrieves all messages in order.pop_item() -> dict | None
: Gets and deletes the last message.clear_session()
: Deletes all messages in the session.🧪 How to Test:
Set the
NEON_DB_URL
environment variable with your PostgreSQL connection string.Run the
main.py
script to:Optionally, call
clear_session()
to reset memory.⚙️ Tech Stack: