3 comments
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.<p>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.<p>Are you handling session isolation between concurrent agents? That seems like it would be critical for avoiding state pollution.
Yes. Browser4 supports concurrent multi-agent execution. At the moment, we support the following scenarios:<p>A single agent operating on multiple pages (tabs) within the same browser context<p>Multiple agents operating in parallel across multiple browser contexts, where each context has an isolated profile<p>Are you specifically looking for multiple agents concurrently operating on the same browser context? If so, could you describe the concrete use case?
Very much excited about this.
*Hybrid extraction: ML agent driven extraction<p>This is what I have been missing in the existing systems
Therefore, we should not be paying for tokens, but for more effective agents.