feat(memory): use event metadata for session/agent state identification #244
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.
Summary
session_{session_id},agent_{agent_id}) with event metadata for identifying session and agent state eventsFixes #220
Fixes #196
Changes
Event Metadata for State Identification
StateTypeenum (SESSION, AGENT) and metadata constants (STATE_TYPE_KEY,AGENT_ID_KEY)Backwards Compatibility
Bug Fixes
list_eventswhere API returns nextToken even with 0 results, causing metadata filter mismatch errors_retry_with_backoffto handle eventual consistency when reading newly created agentsTest plan
Future Work
The following improvements are planned for subsequent PRs: