feat: enable memory in agentcore dev#801
Merged
Hweinstock merged 1 commit intoaws:mainfrom Apr 9, 2026
Merged
Conversation
padmak30
approved these changes
Apr 9, 2026
notgitika
approved these changes
Apr 9, 2026
Hweinstock
approved these changes
Apr 9, 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.
Description
Enables memory support in
agentcore devby injecting deployed memory IDs as environment variables into the local dev server process. Previously, the dev server showed a blanket warning that memory was unavailable locally. Now, if memories have been deployed viaagentcore deploy, their IDs are read from deployed state and passed asMEMORY_<NAME>_IDenv vars — allowing agents to use memory during local development.Changes:
memory-env.tsmodule that reads deployed state and generatesMEMORY_*_IDenv vars from all deployment targets.env.localoverrides taking precedenceagentcore deployand restart dev"getMemoryEnvVarscovering deployed memories, multiple targets, missing state, and edge casesType of Change
Testing
How have you tested the change?
npm run test:unitandnpm run test:integnpm run typechecknpm run lintsrc/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsManual testing was done with a Strands agent only. Other agent frameworks have not been tested.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.