password-app
2 months ago
The concurrency aspect is interesting - we're building password automation and one of the pain points is that most sites have rate limiting / bot detection that gets triggered if you try to parallelize password changes too aggressively.
Sequential execution with realistic timing delays is actually necessary for our use case. But I can see how other agent applications would benefit from true concurrency.
Are you handling session isolation between concurrent agents? That seems like it would be critical for avoiding state pollution.
galaxyeye
2 months ago
Yes. Browser4 supports concurrent multi-agent execution. At the moment, we support the following scenarios:
A single agent operating on multiple pages (tabs) within the same browser context
Multiple agents operating in parallel across multiple browser contexts, where each context has an isolated profile
Are you specifically looking for multiple agents concurrently operating on the same browser context? If so, could you describe the concrete use case?