agent core browser should use persistent context for built-in feature… #288
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
AgentCoreBrowser has some issue to use browser extension due to Playwright non-persistent context is using. This blocks Strands agent customer using session replay feature.
When customers use Playwright to connect to AgentCore browser (for example, via connectOverCDP()), any code that creates a non-persistent browser context (e.g. browser.newContext()) will find that Chrome extensions do not run inside that context — even if the remote browser itself was launched with extensions enabled.
Customer experience:
When this occurs:
Related Issues
Issue is found during test
Documentation PR
N/A
Type of Change
Bug fix
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepareAfter the fix, session replay feature works.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.