You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed there is a gap in the user experience in the sidebar. There are 3 important ingress points that are not available in the sidebar, and their absence creates confusion in the mind of the user: 1/ view, 2/ output, and 3/ trace. They are only accessible by clicking the GenAIScript in the status bar and the clicking through from the dropdown while the script is running, but there is a discoverability problem with that. The users often use the sidebar to start their journey. I think there should be a way to find these actions in the sidebar as well while the script is running...
The text was updated successfully, but these errors were encountered:
The description effectively highlights a key usability concern regarding the GenAIScript sidebar. The identified "ingress points" – view, output, and trace – are crucial for user workflow and the lack of direct access from the sidebar is a recognized pain point.
To further clarify the issue, could you estimate the frequency with which users attempt to access these functionalities through the status bar versus the dropdown while the script is running? This data would be valuable in understanding the severity of the usability problem.
I noticed there is a gap in the user experience in the sidebar. There are 3 important ingress points that are not available in the sidebar, and their absence creates confusion in the mind of the user: 1/ view, 2/ output, and 3/ trace. They are only accessible by clicking the GenAIScript in the status bar and the clicking through from the dropdown while the script is running, but there is a discoverability problem with that. The users often use the sidebar to start their journey. I think there should be a way to find these actions in the sidebar as well while the script is running...
The text was updated successfully, but these errors were encountered: