Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT]: AI generated thread titles #2699

Open
scottybo opened this issue Nov 22, 2024 · 2 comments
Open

[FEAT]: AI generated thread titles #2699

scottybo opened this issue Nov 22, 2024 · 2 comments
Labels
enhancement New feature or request feature request

Comments

@scottybo
Copy link

What would you like to see?

Currently when a new thread is created, the title on the left panel is the beginning of the first sentence. It would be useful if the LLM chosen for the workspace is used to generate a more descriptive title, similar to how the major platforms handle this.

A simple method would be to use an {action} {thing} approach.

For example, if I was asking how to build a brick wall, I might write "How do I build a brick wall?" in a thread.

If this was converted to {action} {thing} it would be:

{Building} {a brick wall}

And the prompt to the LLM could be.

Based on the user's initial input, concisely create a title for this conversation in the format of: {action} {thing}. For example 'building' (action) 'a brick wall' (thing)

@scottybo scottybo added enhancement New feature or request feature request labels Nov 22, 2024
@timothycarambat timothycarambat changed the title [FEAT]: Thread titles should be descriptive instead of showing the start of the first sentence [FEAT]: AI generated thread titles Nov 22, 2024
@timothycarambat
Copy link
Member

Referencing this comment as to why this is currently not the case
#2262 (comment)

@scottybo
Copy link
Author

@timothycarambat I get the thinking behind it, but I'd disagree that it's a minor UX issue.

I tend to start all my chats with variants on the theme of 'please can you...', so all the threads start with the same text.

Perhaps it's something that can be a toggled feature? For me, the latency isn't noticeable because I'm using frontier models on desktop. I'm also focused on the chat so I'm not waiting to see when the thread updates.

If I adjusted the pull request to make it an optional feature would that make more sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants