langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Can the name of the session not be automatically generated and displayed according to the question #14100

New Issue
Closed
opened 2026-02-21 19:15:33 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:15:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @fdj-123 on GitHub (May 21, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Can the name of the session not be automatically generated and displayed according to the question

2. Additional context or comments

Can the name of the session not be automatically generated and displayed according to the question

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @fdj-123 on GitHub (May 21, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Can the name of the session not be automatically generated and displayed according to the question ### 2. Additional context or comments Can the name of the session not be automatically generated and displayed according to the question ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:15:33 -05:00
yindo closed this issue 2026-02-21 19:15:33 -05:00
yindo commented 2026-02-21 19:15:33 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 21, 2025):

Duplicated https://github.com/langgenius/dify/pull/18646

@crazywoola commented on GitHub (May 21, 2025): Duplicated https://github.com/langgenius/dify/pull/18646
yindo commented 2026-02-21 19:15:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 21, 2025):

The ability for session names to be automatically generated and displayed according to the user's question is supported in Dify, but there are some important details to consider:

  • In previous versions and configurations, session titles in the Chat Assistant were automatically summarized based on the user's question. However, if you are seeing session names default to "New Conversation" instead, this is likely due to the model being used.
  • When using the DeepSeek-R1 model or certain alternative models, automatic session title summarization is disabled, and the default "New Conversation" title is shown. To restore automatic session name generation, you need to switch back to the default system model or a faster model in your system models settings. This will allow the system to generate conversation names based on the user's input as before [source] [source].

If you want to customize session naming further, Dify also provides an API for renaming conversations, which can be used to programmatically set or update session names as needed [source].

If you have specific requirements for how session names should be generated or displayed beyond the current functionality, you may need to explore further customization or propose an enhancement.

To continue talking to Dosu, mention @dosu-bot.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (May 21, 2025): <!-- Answer --> The ability for session names to be automatically generated and displayed according to the user's question is supported in Dify, but there are some important details to consider: - In previous versions and configurations, session titles in the Chat Assistant were automatically summarized based on the user's question. However, if you are seeing session names default to "New Conversation" instead, this is likely due to the model being used. - When using the DeepSeek-R1 model or certain alternative models, automatic session title summarization is disabled, and the default "New Conversation" title is shown. To restore automatic session name generation, you need to switch back to the default system model or a faster model in your system models settings. This will allow the system to generate conversation names based on the user's input as before [[source]](https://github.com/langgenius/dify/issues/16219) [[source]](https://github.com/langgenius/dify/issues/15990). If you want to customize session naming further, Dify also provides an API for renaming conversations, which can be used to programmatically set or update session names as needed [[source]](https://github.com/langgenius/dify/blob/main/web/i18n/en-US/app-api.ts). If you have specific requirements for how session names should be generated or displayed beyond the current functionality, you may need to explore further customization or propose an enhancement. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://go.dosu.dev/dosubot), mention @dosu-bot.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/658626b4-c019-4f7f-8713-99f98df52010?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
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: langgenius/dify#14100
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?