cc <@U06RMLQGNGM> <https://github.com/All-Hands-AI...
# proj-agent-canvas
f
cc @breezy-kilobyte-39430 https://github.com/All-Hands-AI/OpenHands/pull/8957, any ideas on how to make the timestamp less prominent? It isn't super important and takes too much space
👀 1
p
move it top-right? make it relative, e.g.: "2 mins ago" and make the date appear only when hovering over the step (could also show absolute date when hovering over, in case you review past day's SWE-agent work?) more importantly, some steps (like condensation) do take a long(er) time; it would be nice to see duration in these cases?
l
I think it should go bottom right, barely visible. People want to read text first, timestamp is not that important.
👍 1
p
also input tokens, cached, output tokens, and estimate price for each step? radical transparency, so we can better begin to intuit what's going on?
l
I tried the PR, and unless the UI is changed so that the assistant messages also come in bubbles, I don't think there's a place for a timestamp that would look good/consistent. I don't really think this should have been a first good issue, it's not the kind of design changes new devs should take. Maybe it's better to put it on hover along with other message details? Showing token/cost might have a chilling factor though.
😄 1
The new conversation UI mockup uses bubbles for the assistant messages as well, A timestamp would look fine there.
b
bottom right (and even outside of the container) make 2 points smaller
My recommendation though is to not show the date (only time) if same day, no italics,
The other note is to maybe not have it visible until hover (to keep the UI a less cluttered)
f
Since we prefer to keep it subtle, I think the best alternatives are either placing it in a message info popup or showing it outside the container on hover. I'll leave a comment on the PR later today. Thank you very much for your feedback @polite-architect-52194 and @little-architect-38123!
l
Np. Not many options without a clear visual separation in assistant messages. One alternative could be changing the copy button into a split button, or replacing it with a "..." button that opens a popup menu with "Copy" and other details below, though neither are consistent choices. The "..." button might work well with the upcoming fork functionality (e.g., adding a "Fork conversation" menu entry), but still not good design choice.
👍 1