starred/anything-llm

Fork 0

mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-03-02 22:57:05 -05:00

[FEAT]: Deprecate `default` thread - Thread UX improvements #2329

New issue

Open

opened 2026-02-28 06:04:06 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 06:04:06 -05:00

Owner

Originally created by @timothycarambat on GitHub (Apr 1, 2025).

Originally assigned to: @timothycarambat on GitHub.

What would you like to see?

We should finally remove the default thread function. It has historically existed since we added threads after we had workspace. The flow should be similar to the video here.

As a user, I click on a workspace:
If no threads are present:

I should see an italic "New thread" title that is currently selected. The first message will update its name and save the thread.
I cannot see the "Create thread" button since I am on the only active thread.

If threads are present in a workspace:

I am automatically loaded into the first available thread if none is selected.
We can also keep track of last active thread within a workspace to when navigating to generic workspace path we auto-load the last active thread. If they click a specific thread, we bring them to that thread.
Can also create a new thread in this UI.

For backwards compatibility:

If the user has chats in the default thread, we will show it. If it is empty, we will not surface this thread to the user and the first condition above will apply here for UX.

Originally created by @timothycarambat on GitHub (Apr 1, 2025). Originally assigned to: @timothycarambat on GitHub. ### What would you like to see? We should finally remove the `default` thread function. It has historically existed since we added threads _after_ we had workspace. The flow should be similar [to the video here](https://www.loom.com/share/ff0c50d87f974cbda0c68d2cfc4fb1b5). As a user, I click on a workspace: If no threads are present: - I should see an italic "New thread" title that is currently selected. The first message will update its name and save the thread. - I cannot see the "Create thread" button since I am on the only active thread. If threads are present in a workspace: - I am automatically loaded into the first available thread if none is selected. - We can also keep track of last active thread within a workspace to when navigating to generic workspace path we auto-load the last active thread. If they click a specific thread, we bring them to that thread. - Can also create a new thread in this UI. For backwards compatibility: - If the user **has chats** in the default thread, we will show it. If it is empty, we will not surface this thread to the user and the first condition above will apply here for UX.

deekerman added the

enhancement

UI/UX

feature request

labels

2026-02-28 06:04:06 -05:00

deekerman commented

2026-02-28 06:04:09 -05:00

Author

Owner

@scottybo commented on GitHub (Apr 2, 2025):

Great to see this being implemented! A few thoughts on the implementation:

Clicking on a workspace with threads

I'd recommend against loading the most recent thread when going to a workspace. Usually when returning to a chat platform, you're going to start a new conversation. To remove friction, when you click on a workspace, the chat window should show and only when a conversation is started does it create the new thread.

Alternatively, perhaps this could be a setting as I image preferences will vary on this one.

Backwards compatibility

It would be good to be able to delete the default thread - I've frequently accidentally started a "new" conversation in the default thread.

@scottybo commented on GitHub (Apr 2, 2025): Great to see this being implemented! A few thoughts on the implementation: **Clicking on a workspace with threads** I'd recommend against loading the most recent thread when going to a workspace. Usually when returning to a chat platform, you're going to start a new conversation. To remove friction, when you click on a workspace, the chat window should show and only when a conversation is started does it create the new thread. Alternatively, perhaps this could be a setting as I image preferences will vary on this one. **Backwards compatibility** It would be good to be able to delete the default thread - I've frequently accidentally started a "new" conversation in the default thread.

deekerman commented

2026-02-28 06:04:09 -05:00

Author

Owner

@pcfreak30 commented on GitHub (Nov 2, 2025):

It would be good to be able to delete the default thread - I've frequently accidentally started a "new" conversation in the default thread.

Just started messing with anything, and this is the most annoying thing ive hit so far. I cant delete the default chat, but i can delete all others.

@pcfreak30 commented on GitHub (Nov 2, 2025): > It would be good to be able to delete the default thread - I've frequently accidentally started a "new" conversation in the default thread. Just started messing with anything, and this is the most annoying thing ive hit so far. I cant delete the default chat, but i can delete all others.

deekerman commented

2026-02-28 06:04:09 -05:00

Author

Owner

@linux-universe commented on GitHub (Jan 17, 2026):

anything (Ha! that joke wasn't planned) holding this back?

@linux-universe commented on GitHub (Jan 17, 2026): **anything** (Ha! that joke wasn't planned) holding this back?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/anything-llm#2329

No description provided.

Rows
Columns

[FEAT]: Deprecate default thread - Thread UX improvements #2329

What would you like to see?

[FEAT]: Deprecate `default` thread - Thread UX improvements #2329