We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Currently we have three types of agent (doc):
These existing agent types have limitations in supporting complex logic. Specifically, they lack the ability to:
This limitation restricts the creation of more sophisticated and efficient workflows within OpenSearch.
What solution would you like? We propose implementing a new type of agent that supports a graph-style workflow. This Graph-Based Workflow Agent would:
This new agent type would significantly enhance OpenSearch's capability to handle complex, multi-step processes and decision-making workflows.
What alternatives have you considered? Enhance current flow type.
The text was updated successfully, but these errors were encountered:
I would like to work on this, can you please assign this to me?
Sorry, something went wrong.
@ylwu-amzn , this solution is planned for which release? Thanks
pyek-bot
No branches or pull requests
Is your feature request related to a problem?
Currently we have three types of agent (doc):
These existing agent types have limitations in supporting complex logic. Specifically, they lack the ability to:
This limitation restricts the creation of more sophisticated and efficient workflows within OpenSearch.
What solution would you like?
We propose implementing a new type of agent that supports a graph-style workflow. This Graph-Based Workflow Agent would:
This new agent type would significantly enhance OpenSearch's capability to handle complex, multi-step processes and decision-making workflows.
What alternatives have you considered?
Enhance current flow type.
The text was updated successfully, but these errors were encountered: