Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #5739] [MERGED] Kill default thread #5549

New Issue
Closed
opened 2026-06-05 15:21:42 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 15:21:42 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/5739
Author: @timothycarambat
Created: 6/1/2026
Status: ✅ Merged
Merged: 6/1/2026
Merged by: @timothycarambat

Base: master ← Head: kill-default-thread

📝 Commits (3)

📊 Changes

4 files changed (+81 additions, -24 deletions)

View changed files

📝 frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/index.jsx (+33 -16)
📝 frontend/src/components/WorkspaceChat/ChatContainer/index.jsx (+35 -4)
📝 frontend/src/models/workspaceThread.js (+3 -3)
📝 server/endpoints/workspaceThreads.js (+10 -1)

📄 Description

Pull Request Type

  • ✨ feat (New feature)
  • 🐛 fix (Bug fix)
  • ♻️ refactor (Code refactoring without changing behavior)
  • 💄 style (UI style changes)
  • 🔨 chore (Build, CI, maintenance)
  • 📝 docs (Documentation updates)

Relevant Issues

resolves #3577
resolves #5431
resolves #4531

Description

  • Kills the legacy default thread on workspaces
  • Does not change any backend functionality. This is now purely frontend UI/UX. Backend still fully supports default/null thread.
  • If the user has chats on the default thread, it will still be visible in the UI, but new workspaces will not show it.
  • /reseting the default thread will also hide it from thread UI as well.

Visuals (if applicable)

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated (if applicable)
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/5739 **Author:** [@timothycarambat](https://github.com/timothycarambat) **Created:** 6/1/2026 **Status:** ✅ Merged **Merged:** 6/1/2026 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `kill-default-thread` --- ### 📝 Commits (3) - [`1767ca3`](https://github.com/Mintplex-Labs/anything-llm/commit/1767ca3f2dbdb9593b96e633b2abc556acc11c7f) no more default thread - [`413ae26`](https://github.com/Mintplex-Labs/anything-llm/commit/413ae2640d73086c5b39004d6e26ec714b22bcce) lint - [`3c6b741`](https://github.com/Mintplex-Labs/anything-llm/commit/3c6b74169abe6319d21685a01cac4adc4665f2a7) Merge branch 'master' into kill-default-thread ### 📊 Changes **4 files changed** (+81 additions, -24 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/index.jsx` (+33 -16) 📝 `frontend/src/components/WorkspaceChat/ChatContainer/index.jsx` (+35 -4) 📝 `frontend/src/models/workspaceThread.js` (+3 -3) 📝 `server/endpoints/workspaceThreads.js` (+10 -1) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [x] ✨ feat (New feature) - [ ] 🐛 fix (Bug fix) - [ ] ♻️ refactor (Code refactoring without changing behavior) - [ ] 💄 style (UI style changes) - [x] 🔨 chore (Build, CI, maintenance) - [ ] 📝 docs (Documentation updates) ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #3577 resolves #5431 resolves #4531 ### Description - Kills the legacy `default` thread on workspaces - Does **not** change any backend functionality. This is now purely frontend UI/UX. Backend still fully supports default/null thread. - If the user has chats on the default thread, it will still be visible in the UI, but new workspaces will not show it. - `/reset`ing the default thread will also hide it from thread UI as well. <!-- Describe the changes in this PR that are impactful to the repo. What problem does it solve? --> ### Visuals (if applicable) <!-- Add screenshots or screen recordings to demonstrate the changes, especially for UI updates. --> ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> ### Developer Validations <!-- All of the applicable items should be checked. --> - [ ] I ran `yarn lint` from the root of the repo & committed changes - [ ] Relevant documentation has been updated (if applicable) - [ ] I have tested my code functionality - [ ] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 15:21:42 -04:00
yindo closed this issue 2026-06-05 15:21:42 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5549
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?