7 pointsby galaxyeye2 months ago3 comments
  • password-app2 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.

    • galaxyeyea month 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?

  • SkyRocknRoll2 months ago
    Very much excited about this. *Hybrid extraction: ML agent driven extraction

    This is what I have been missing in the existing systems

    • galaxyeye2 months ago
      Thank you for your comment. I think X-SQL based extraction could also be useful: its ideal for high-complexity data-extraction pipelines with multiple-dozen entities and several hundred fields per entity. What are your thoughts on this idea?
  • tomfox22 months ago
    Therefore, we should not be paying for tokens, but for more effective agents.
    • galaxyeye2 months ago
      Yes, that's why we develop it. And I think X-SQL based extraction could also be useful: its ideal for high-complexity data-extraction pipelines with multiple-dozen entities and several hundred fields per entity. What are your thoughts on this idea?