Separate Workspaces, Shared Chat, and Task Control

A multi-agent browser system gives each worker:

• Its own Chrome instance.
• Its own workspace.
• Its own MCP server.
• Its own local instructions.
• Its own task assignment.

The agents communicate with a centralized shared chat or file. The orchestrator can reset the shared state at the beginning of a run, assign work, and check the chat periodically for progress, problems, and results.

A typical process is:

1. Determine how many agents are required.
2. Launch the browser instances.
3. Reset the shared communication file.
4. Divide the target list.
5. Give each agent its assigned targets.
6. Allow each agent to navigate and act independently.
7. Have agents report problems or completed work to the shared chat.
8. Let the orchestrator inspect progress and reassign work if necessary.
9. Collect and validate the final results.

The shared communication layer prevents every browser agent from operating as an isolated black box. It also allows an agent that encounters a problem to report it without stopping the entire operation.