Description

The Rovo full-screen chat interface is functional but lacks several UX elements that are standard in comparable AI chat interfaces. Individually these are minor, but collectively they make it difficult to manage, navigate, and work effectively with Rovo conversations over time - particularly for power users and administrators who rely on Rovo regularly.

Chat naming should be model-generated, not truncated input

Currently, each chat in the sidebar is named using the beginning of the first message the user sent, truncated to fit the available space. This results in a list of largely indistinguishable entries (e.g., multiple "Can you read this page?" entries as visible in the current UI). Rovo should generate a contextually relevant name for each conversation based on its content, in the same way that other AI chat interfaces (e.g., Claude, ChatGPT) summarise conversations into meaningful titles. Users can already rename chats manually, but the default should be useful without requiring manual intervention.

Chat header should reflect the active conversation

When inside a chat, the header area does not update to reflect anything about the conversation the user is in. The only indication that a specific chat is active is the highlighted menu item in the left sidebar. The header should display the chat name (whether model-generated or user-renamed) so the user has clear context about which conversation they are working in without relying on the sidebar.

Chat timestamps should be specific and per-conversation

The sidebar groups chats under coarse time labels ("This past week", "This past month") without specifying which data point the label refers to (creation date? last message?). Each chat should display its own specific timestamp showing when it was last active, with sufficient vertical padding to accommodate this without cluttering the sidebar. Coarse groupings are acceptable as section headers, but they are not a substitute for per-conversation timestamps.

Ability to favourite or pin chats

The only chat management options currently available are rename and delete (via the three-dot menu). There is no ability to favourite, star, or pin a chat. For users who are actively working across multiple conversations, the ability to pin important chats to the top of the list is a basic organisational requirement that prevents active work from being buried as new conversations are created.

Chat folders or grouping

There is no ability to organise chats into folders or categories. As the number of conversations grows, the flat chronological list becomes increasingly difficult to navigate. Supporting user-defined folders or groups would allow users to categorise conversations by topic, project, or purpose - for example, separating support conversations from research conversations from administrative work.

Attachments should be considered automatically

When a user uploads an attachment to a Rovo message, Rovo does not appear to consider the attachment's contents unless the user explicitly asks Rovo to refer to it. Attaching a file to a message is an implicit signal that the contents are relevant to the conversation. Rovo should automatically consider attachment contents as part of the message context without requiring a separate prompt.

Copy function should support content-only output

When copying Rovo's output, the copied content includes conversational commentary alongside the actual content the user requested. Rovo should support a "copy content only" function that strips Rovo's conversational framing and provides only the substantive output. For example, if a user asks Rovo to draft a message, the copy function should provide the drafted message without Rovo's preamble ("Here's a draft for you...") and postamble ("Let me know if you'd like me to adjust...").

Business Justification for these suggestions

Rovo can be deployed at Atlassian customers as the first-line support interface for thousands of power users and more. Administrators and power users interact with Rovo frequently and accumulate a high volume of conversations. The current interface makes it difficult to manage, locate, and return to previous conversations efficiently. These improvements would bring the Rovo chat experience in line with the standard set by comparable AI chat products and improve adoption and trust in the tool.