Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
@voltagent_postgres@0.1.9 source code.tar.gz | 2025-07-25 | 3.4 MB | |
@voltagent_postgres@0.1.9 source code.zip | 2025-07-25 | 4.0 MB | |
README.md | 2025-07-25 | 1.9 kB | |
Totals: 3 Items | 7.4 MB | 0 |
Patch Changes
-
#418
aa024c1
Thanks @omeraplak! - fix: memory storage implementations now correctly return the most recent messages when using context limitFixed an issue where memory storage implementations (LibSQL, PostgreSQL, Supabase) were returning the oldest messages instead of the most recent ones when a context limit was specified. This was causing AI agents to lose important recent context in favor of old conversation history.
Before:
contextLimit: 10
returned the first 10 messages (oldest)- Agents were working with outdated context
After:
contextLimit: 10
returns the last 10 messages (most recent) in chronological order- Agents now have access to the most relevant recent context
- InMemoryStorage was already working correctly and remains unchanged
Changes:
- LibSQLStorage: Modified query to use
ORDER BY DESC
withLIMIT
, then reverse results - PostgreSQL: Modified query to use
ORDER BY DESC
withLIMIT
, then reverse results - Supabase: Modified query to use
ascending: false
withlimit
, then reverse results
This ensures consistent behavior across all storage implementations where context limits provide the most recent messages, improving AI agent response quality and relevance.
-
Updated dependencies [
67450c3
,aa024c1
,aa024c1
]:- @voltagent/core@0.1.67