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.
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.