3 comments

  • password-app7 hours ago
    The concurrency aspect is interesting - we&#x27;re building password automation and one of the pain points is that most sites have rate limiting &#x2F; 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.
  • SkyRocknRoll2 days ago
    Very much excited about this. *Hybrid extraction: ML agent driven extraction<p>This is what I have been missing in the existing systems
    • galaxyeye1 day 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 days ago
    Therefore, we should not be paying for tokens, but for more effective agents.
    • galaxyeye1 day ago
      Yes, that&#x27;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?