Currently the browser in the agents interface appears to be shared across agent sessions. Now that I can have multiple sessions across potentially multiple repositories, this feels incorrect. I would like to have a browser scoped to each session so that the browser mcp in one agent session does not interfere with the browser in any other agent session.
Hey, thanks for the request. This is a known limitation. Right now the browser instance is shared across agent sessions, so when they run in parallel they can interfere with each other.
As a temporary workaround, you can stagger browser tasks so only one agent uses the browser at a time. Sometimes an explicit prompt instruction like “open a new browser tab” helps, but it isn’t 100% reliable since the cause is architectural.
The team is aware of the issue. I’ve passed along your feedback, especially for the Agents Window with multi-sessions where this becomes more critical. Let me know if you have any questions.
Hi, is there a way we can control if the browser session should be shared? For example i work on a huge frontend repo and building/loading a new tab for each session is overkill, because i usually open new agent sessoins when my context limit is reached and feel like quality of output is getting lower. But instead of having to open browser tab again, it would be good if i can just reuse the old browser that is already running
Hey, thanks for the feedback. Right now there isn’t a toggle for this. The browser is shared across sessions by default, but you can’t control its behavior yet, like reusing the existing one vs opening a new tab for each session.
Your case is interesting because it’s kind of the opposite of the original request in that thread. They want per-session isolation, but you want to reuse an already running browser so you don’t have to rebuild a heavy frontend every time. In the end both point to the same need, having a way to control this behavior.
Yeap saw that! I think having the option to choose will be really useful. When working on multiple small sites - yes multi tab is definitely the way. But when i have multiple agents working on a big repo, i would like a shared browser so i can see the changes