feat: isolated browser tabs for parallel MCP sessions #70
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
When multiple MCP clients call
oracle consultin parallel (e.g., multiple Claude Code sessions), browser mode sessions can contaminate each other because they share the same Chrome tab. This PR fixes the issue by creating isolated tabs for each session.Changes:
connectWithNewTab()andcloseTab()functions to create/cleanup isolated CDP tabsrunBrowserModeinstead of connecting to the shared first targetmanualLoginandchatgptUrlfrom user's~/.oracle/config.jsonto MCP consult toolBefore: Parallel sessions share one tab → responses get mixed up
After: Each session gets its own tab → responses are isolated
Test plan
oracle consultcalls with different prompts🤖 Generated with Claude Code