Closed 20001LastOrder closed 6 days ago
One potential issue associated with this is that the library we used for state management supports many types of state management. Each type uses different types of state. We need to investigate whether we can support all of them or we should only select one.
PROBLEM Currently, the prompt for selecting actions is fixed in the policy, e.g. ReACT Policy.
However, with the state management implementation, one may want to have different prompts for selecting the next actions based on the state the agent is currently in. Thus, we should support config prompt at the state level.
(In the current implementation, the states have only names for identifying them, no descriptions or examples. This makes routing / navigating the state machine inaccurate.)
SOLUTION
Make use of the state machine library's support for extensions to include descriptive information for state machine nodes, and use this info at decision-making time. This is implemented on the experimental branch.