fix(gateway): reset _last_flushed_db_idx when reusing cached agent#32760
Open
ArgoBaseBot wants to merge 1 commit into
Open
fix(gateway): reset _last_flushed_db_idx when reusing cached agent#32760ArgoBaseBot wants to merge 1 commit into
ArgoBaseBot wants to merge 1 commit into
Conversation
Cached AIAgent instances retain _last_flushed_db_idx from previous turns. When the agent is reused, the stale index causes _flush_messages_to_session_db to skip user messages that fall below the old flush cursor, silently dropping them from state.db. This manifests as persistent context loss — every turn shows history=0 even after multiple exchanges. Reset the flush cursor in _init_cached_agent_for_turn so each turn starts with a clean flush state.
19 tasks
This was referenced Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cached AIAgent instances retain _last_flushed_db_idx from previous turns. When the agent is reused, the stale index causes _flush_messages_to_session_db to skip user messages that fall below the old flush cursor, silently dropping them from state.db. This manifests as persistent context loss — every turn shows history=0 even after multiple exchanges.
Reset the flush cursor in _init_cached_agent_for_turn so each turn starts with a clean flush state.
What does this PR do?
Related Issue
Fixes #
Type of Change
Changes Made
How to Test
Checklist
Code
fix(scope):,feat(scope):, etc.)pytest tests/ -qand all tests passDocumentation & Housekeeping
docs/, docstrings) — or N/Acli-config.yaml.exampleif I added/changed config keys — or N/ACONTRIBUTING.mdorAGENTS.mdif I changed architecture or workflows — or N/AFor New Skills
hermes --toolsets skills -q "Use the X skill to do Y"Screenshots / Logs