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.
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?
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?
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.
This is what I have been missing in the existing systems