It is kind of confusing to have a "Conversations" ...
# proj-agent-canvas
e
It is kind of confusing to have a "Conversations" and "New Conversation" button both on the nav. They effectively do the same thing - bring you to a UI to start a new conversation.
h
Paul has a PR that tries to fix that exact UX issue https://github.com/OpenHands/agent-canvas/pull/340
🙌 1
w
"new conversation" does not bring you to the UI! it lets you create a convo with one click
I find this important
well...two clicks
@breezy-kilobyte-39430 IMO we need this "quick launch"
I'm in one convo, and I want to quickly get another one going--I don't want to swap into the homepage UI
b
I think the answer is to put the contents of New Conversation in to a modal, not a dropdown, but then we have the issue of building out the newer Start Conversation page which the user comes to by default. In my update I hid the newer one-click button because it is an oddity to have multiple New Conversation buttons. My recommendation is to incrementally improve this. When we have a proper blank conversation page that is the default home we can have the one click New Conversation.
w
I agree on incremental improvement! I also agree we shouldn't have two UIs for creating a convo IMO it'd be better to kill the current homepage than to kill this button though--it's what keeps me in flow state
b
What about a fast follow? There's a number of major design housekeeping tasks that need to be done with the features of canvas already being released? Right now, at least the design isn't broken, the new button breaks design conventions across our products. We could have a keyboard command that initiates a new conversation until we have the full design fix for canvas and the saas experience.
w
tbh I'd rather a fast follow that fixes the design than one that temporarily interrupts my workflow 🙂 I think this is critical UX for anyone seriously using Canvas as a daily driver what's hard about fixing how it's displayed right now?
b
Working on it! What's hard is the whack-a-mole of design debt—honest answer. 🙂 Trying to make sure it "looks good, feels good" as much as possible.
w
nod yeah I hear you!
I'd love to put a skill into the repo that describes our style guide. That should keep the agent on the rails as we vibecode
getting as many reusable components in there as possible would be helpful too