Chat appears in multiple date groups in the sidebar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
No files are named in the report. Start by finding the sidebar chat-history component and the code that assigns each chat to a date bucket such as Today or Previous 7 days; check which timestamp field feeds the grouping and whether one chat can be rendered into two buckets. Reproduce using the listed steps and the two screenshots, then confirm the chat appears once, in the bucket its authoritative creation or last-activity timestamp implies.
Written by the indexing model from the issue text.
Description
Version
0.1.7
Platform
Windows 11 x64
Description
Bug: Chat appears in multiple date groups in the sidebar
Category: UI / Chat History / Sidebar
Severity: Medium
Environment: Self-hosted Open WebUI
Deployment: Docker
Version: ghcr.io/open-webui/open-webui:main
Instance: ai.trikon.cloud
Description
A chat titled hi appears in two different date-based groups in the sidebar simultaneously:
- Today
- Previous 7 days
The sidebar appears to show the same chat in multiple date buckets, creating ambiguity about which entry represents the actual conversation.
Steps to reproduce
- Sign in to the Open WebUI instance.
- Create or open a chat with a short message such as
Hi. - Allow the chat title to be generated.
- Inspect the sidebar chat-history groups.
- Observe the entries under Today and Previous 7 days.
Actual behaviour
The chat titled hi appears under both Today and Previous 7 days. The older listing displays a 4d timestamp.
Expected behaviour
Each chat should appear exactly once in the sidebar.
The chat should be assigned to the appropriate date group based on its authoritative creation or last-activity timestamp, according to the intended grouping behaviour.
Evidence
Two screenshots attached showing the duplicate hi entries and the current conversation.
Impact
- Duplicate chat-history entries.
- Confusion when navigating chat history.
- Reduced confidence in the accuracy of date-based grouping.
Steps to reproduce
No response
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 130
- Forks
- 8
- Avg merge
- 1m
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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 open-webui/tether
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
open-webui/tether#51 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
open-webui/tether#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
open-webui/tether#49 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
open-webui/tether#48 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
open-webui/tether#44 ·
Maintainers usually reply within 1 day
All issues in open-webui/tether
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/void#835 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AykutSarac/jsoncrack.com#616 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melgarafael/DeskcommCRM#4679 ·
Maintainers usually reply within 1 day
-
enhancement size:medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day