-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
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
[Chat UI] Agent Creation Dropdown Inputs #897
Labels
Comments
(reopening since the backend needs to be updated for non-placeholder, assigned to @cpacker) |
This issue has been automatically closed due to 60 days of inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, in the Chat UI for creating an agent, there are four text input fields: 'name', 'human', 'persona', and 'model'. The issue is that these fields require manual input every time, which can be time-consuming and prone to inconsistency, especially if there are predefined, commonly used values that could be selected.
Describe the solution you'd like
I propose to enhance these text input fields by converting them into dropdown menus that populate with values retrieved from the database. This would streamline the agent creation process by allowing users to select from a list of predefined, frequently used options. Additionally, to maintain flexibility, the fields should also support manual text input for cases where the desired value is not in the dropdown. This dual approach (dropdown with a manual input option) would cater to both common and unique agent creation scenarios.
Describe alternatives you've considered
An alternative could be the implementation of an auto-complete feature for these text fields. As users begin to type, suggestions based on existing database entries could appear. Although this might not be as user-friendly for discovering available options compared to dropdown menus.
Additional context
The change requires backend support for fetching the relevant data to populate the dropdowns, as well as frontend modifications for the UI change.
This will require 2 PRs: One for React and one for the Rest API.
The text was updated successfully, but these errors were encountered: