Skip to content

[Chatbot] - Support inline renaming of conversations in ChatbotConversationHistoryNav #863

Description

@its-mitesh-kumar

Chatbot Component Area

Layout (Chat Drawer, Header, Persona)

Describe the feature

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Needs triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions