patternfly / patternfly/chatbot
[Chatbot] - Support inline renaming of conversations in ChatbotConversationHistoryNav
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 37
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 5
Description
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
textcontent 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
https://github.com/user-attachments/assets/92e7011b-10e9-44da-8e5c-ff1856b509b0
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.
Jira Issue: PF-4392
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ChatbotConversationHistoryNav, the Conversation interface, and the MenuItem/menuItems rendering described in the issue. Trace how conversation titles are displayed and how the kebab actions are handled, then verify that double-click and Rename enter an accessible focused input, Enter confirms, Escape cancels, and both pinned and unpinned items work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100