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
{{ message }}
Repository navigation
[Chatbot] - Support inline renaming of conversations in ChatbotConversationHistoryNav #863
When using ChatbotConversationHistoryNav, there is no built-in support for inline renaming of conversations in the sidebar.
The Conversation interface only accepts a static text string, and the component renders it as plain text inside a MenuItem. There is no way for consumers to switch a conversation item into an inline edit mode without overriding.
To rename a conversation, consumers currently have to build their own modal dialog outside the component, triggered from the menuItems dropdown. An inline rename option — where selecting "Rename" from the kebab menu converts the title into an editable text input in-place — would be a more direct UX and reduce the need for consumer-side workarounds.
Expected Data Structure
No response
Conversational Flow
Inline rename would be triggered from double-clicking the title and the per-conversation kebab menu "Rename" action.
The text content switches to an inline text input pre-filled with the current value
Enter confirms the rename
Escape cancels and reverts to the original text
Applies to all conversation items (pinned and unpinned)
Visuals & Mockups
S_.2026-07-05.at.12.16.48.PM.mov
Conversational Accessibility
The inline text input should receive focus automatically when entering edit mode
Escape key must cancel editing and return focus to the conversation item
Enter key must confirm the rename
The editable input should have an accessible label (e.g., "Rename conversation")
Validation
This request aligns with PatternFly AI/Chatbot design guidelines.
I have searched for existing chatbot-specific components.
One of the reasons we haven't yet implemented this pattern yet is because doing so introduces semantic/accessibility issues.
We're using the PatternFly Menu components to build out the conversation items, which tl;dr of that is each menu is given a role="menu" attribute, and each item within a menu a role="menuitem" attribute. An element with a role of menu expects only menuitem children. Updating a conversation item to be a text input for editing results in a couple problematic results depending how the update is made:
If we simply just replace the role="menuitem" element with a text input, that no longer is semantically correct since the role="menu" element can't contain an input (textbox) role.
If we do the same as above, but give the textinput role='menuitem", it then loses the semantics of being a textinput, so a user may not know they're focused on an input that they can edit.
Activity
its-mitesh-kumar commentedon Jul 6, 2026
Cc: @HusneShabbir @ShiranHi
thatblindgeye commentedon Jul 10, 2026
One of the reasons we haven't yet implemented this pattern yet is because doing so introduces semantic/accessibility issues.
We're using the PatternFly Menu components to build out the conversation items, which tl;dr of that is each menu is given a
role="menu"attribute, and each item within a menu arole="menuitem"attribute. An element with a role of menu expects only menuitem children. Updating a conversation item to be a text input for editing results in a couple problematic results depending how the update is made:role="menuitem"element with a text input, that no longer is semantically correct since therole="menu"element can't contain an input (textbox) role.role='menuitem", it then loses the semantics of being a textinput, so a user may not know they're focused on an input that they can edit.rebeccaalpert commentedon Aug 27, 2026
Hey @its-mitesh-kumar - we're not ready to make the changes that would enable this, but I've spoken to my manager about getting it on the roadmap.