[Chatbot] - Support inline renaming of conversations in ChatbotConversationHistoryNav
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
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.
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
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 37
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 5
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.
More from patternfly/chatbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
patternfly/chatbot#910 · 3 comments ·
-
PF Team
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
patternfly/chatbot#852 ·
-
PF Team
patternfly/chatbot#908 · 1 assignee ·
-
PF Team
Difficulty 4/5 3-5 days Newbie friendliness 48/100
patternfly/chatbot#906 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
patternfly/chatbot#905 · 1 comment ·
All issues in patternfly/chatbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·