fix(web-security): require unique agent-browser session names to avoi…#64
Merged
GangGreenTemperTatum merged 1 commit intoJun 26, 2026
Conversation
…d collisions Add guidance to always use --session <unique-name> when invoking the agent-browser CLI. Without an explicit session name, all callers share the default session and clobber each other's page state — causing flaky failures in concurrent agents or parallel tasks.
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
1 participant
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.
…d collisions
Add guidance to always use --session when invoking the agent-browser CLI. Without an explicit session name, all callers share the default session and clobber each other's page state — causing flaky failures in concurrent agents or parallel tasks.