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

Skip conversation starter #5502

New Issue
Closed
opened 2026-02-21 18:11:17 -05:00 by yindo · 36 comments
yindo commented 2026-02-21 18:11:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @wupeisheng on GitHub (Sep 10, 2024).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

v0.7.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I didn't set up a pre chat that requires users to input some information, but when I first entered the chat box, it showed that I needed to click on start conversation to enter the chat window. I don't want users to click on start conversation again, I want to directly enter the dialog box. I look forward to resolving this issue.

screenshot-20240910-112257
screenshot-20240910-115922

✔️ Expected Behavior

Directly enter the dialog box

❌ Actual Behavior

I need to click on start conversation to enter the chat box

Originally created by @wupeisheng on GitHub (Sep 10, 2024). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version v0.7.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I didn't set up a pre chat that requires users to input some information, but when I first entered the chat box, it showed that I needed to click on start conversation to enter the chat window. I don't want users to click on start conversation again, I want to directly enter the dialog box. I look forward to resolving this issue. ![screenshot-20240910-112257](https://github.com/user-attachments/assets/d3d08a4d-4549-49fe-9831-54c1a4ea2516) ![screenshot-20240910-115922](https://github.com/user-attachments/assets/9142aa1a-252a-4532-8129-5c9b631af3ad) ### ✔️ Expected Behavior Directly enter the dialog box ### ❌ Actual Behavior I need to click on start conversation to enter the chat box
yindo added the 💪 enhancement label 2026-02-21 18:11:17 -05:00
yindo closed this issue 2026-02-21 18:11:17 -05:00
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 10, 2024):

@wupeisheng Hello! I'm here to help you with bug fixes, answer questions, and guide you on how to contribute. If you need assistance, feel free to ask.

To configure the chatbot to directly enter the dialog box without requiring users to click on "Start Conversation," you need to enable the "Conversation Opener" feature during the application orchestration. This feature allows the AI application to automatically initiate the first line of dialogue when a new conversation is created.

Ensure that this feature is enabled in your application settings to achieve the desired behavior [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 10, 2024): <!-- Greeting --> @wupeisheng Hello! I'm here to help you with bug fixes, answer questions, and guide you on how to contribute. If you need assistance, feel free to ask. <!-- Answer --> To configure the chatbot to directly enter the dialog box without requiring users to click on "Start Conversation," you need to enable the "Conversation Opener" feature during the application orchestration. This feature allows the AI application to automatically initiate the first line of dialogue when a new conversation is created. Ensure that this feature is enabled in your application settings to achieve the desired behavior <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-publishing/launch-your-webapp-quickly/conversation-application.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/application-publishing/launch-your-webapp-quickly/conversation-application.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 10, 2024):

We will take a look at this feature once we are free.

@crazywoola commented on GitHub (Sep 10, 2024): We will take a look at this feature once we are free.
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Sep 10, 2024):

一旦我们有空，我们就会查看此功能。

Thank you, I am looking forward to it. This is very important for the user experience in a scenario where no user input information is required

@wupeisheng commented on GitHub (Sep 10, 2024): > 一旦我们有空，我们就会查看此功能。 Thank you, I am looking forward to it. This is very important for the user experience in a scenario where no user input information is required
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@VincePotato commented on GitHub (Sep 11, 2024):

Thank you for your suggestion. We will include it in our product roadmap.

@VincePotato commented on GitHub (Sep 11, 2024): Thank you for your suggestion. We will include it in our product roadmap.
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Sep 24, 2024):

Thank you for your suggestion. We will include it in our product roadmap.

May I ask when this feature is planned to be launched? Thank you

@wupeisheng commented on GitHub (Sep 24, 2024): > Thank you for your suggestion. We will include it in our product roadmap. May I ask when this feature is planned to be launched? Thank you
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@youssefsiam38 commented on GitHub (Oct 22, 2024):

This is a very much needed feature

@youssefsiam38 commented on GitHub (Oct 22, 2024): This is a very much needed feature
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Oct 23, 2024):

感谢您的建议。我们将其纳入我们的产品路线。

@crazywoola
It has been over a month now. Is there a schedule for this issue? It is very, really important for the user experience. Other products such as Fastgpt and MaxKB are supported by default, and we hope to support them as soon as possible!

@wupeisheng commented on GitHub (Oct 23, 2024): > 感谢您的建议。我们将其纳入我们的产品路线。 @crazywoola It has been over a month now. Is there a schedule for this issue? It is very, really important for the user experience. Other products such as Fastgpt and MaxKB are supported by default, and we hope to support them as soon as possible!
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@xjose97x commented on GitHub (Nov 5, 2024):

This is a very much needed feature

@xjose97x commented on GitHub (Nov 5, 2024): This is a very much needed feature
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 6, 2024):

Hi, @wupeisheng. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • A bug in Dify v0.7.3 requires users to click "start conversation" to enter the chat box, even without a pre-chat requirement.
  • I suggested enabling the "Conversation Opener" feature as a workaround.
  • You and others highlighted the importance of this feature for user experience.
  • VincePotato acknowledged the feedback and mentioned it would be added to the product roadmap.
  • You are seeking a timeline for the implementation, noting that similar products support this feature by default.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of Dify. If so, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 6, 2024): Hi, @wupeisheng. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - A bug in Dify v0.7.3 requires users to click "start conversation" to enter the chat box, even without a pre-chat requirement. - I suggested enabling the "Conversation Opener" feature as a workaround. - You and others highlighted the importance of this feature for user experience. - VincePotato acknowledged the feedback and mentioned it would be added to the product roadmap. - You are seeking a timeline for the implementation, noting that similar products support this feature by default. **Next Steps** - Please confirm if this issue is still relevant to the latest version of Dify. If so, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@youssefsiam38 commented on GitHub (Dec 7, 2024):

This issue is still relevant and needed

@youssefsiam38 commented on GitHub (Dec 7, 2024): This issue is still relevant and needed
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@huy302 commented on GitHub (Dec 13, 2024):

This issue is desperately needed, please keep us updated on its timeline

@huy302 commented on GitHub (Dec 13, 2024): This issue is desperately needed, please keep us updated on its timeline
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@kunlun122 commented on GitHub (Dec 25, 2024):

This is a very much needed feature

@kunlun122 commented on GitHub (Dec 25, 2024): This is a very much needed feature
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@kunlun122 commented on GitHub (Dec 29, 2024):

Is there a schedule for this issue? It is very, really important for the user experience

@kunlun122 commented on GitHub (Dec 29, 2024): Is there a schedule for this issue? It is very, really important for the user experience
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@jiguantong commented on GitHub (Jan 15, 2025):

This is very important for user experience and needs to be taken seriously.

@jiguantong commented on GitHub (Jan 15, 2025): This is very important for user experience and needs to be taken seriously.
yindo commented 2026-02-21 18:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@kunlun122 commented on GitHub (Feb 5, 2025):

Any progress?

@kunlun122 commented on GitHub (Feb 5, 2025): Any progress?
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@bsnow0117 commented on GitHub (Feb 7, 2025):

This extra step seems unnecessary for the user experience.

@bsnow0117 commented on GitHub (Feb 7, 2025): This extra step seems unnecessary for the user experience.
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 7, 2025):

WIP

@crazywoola commented on GitHub (Feb 7, 2025): WIP
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Feb 8, 2025):

Any progress?

NO

@wupeisheng commented on GitHub (Feb 8, 2025): > Any progress? NO
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Feb 8, 2025):

在制品

WIP

What is the timeline for publication

@wupeisheng commented on GitHub (Feb 8, 2025): > 在制品 > WIP What is the timeline for publication
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Feb 8, 2025):

WIP

When is the publishing timeline?

@wupeisheng commented on GitHub (Feb 8, 2025): > WIP When is the publishing timeline?
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@haomiemie commented on GitHub (Feb 26, 2025):

Is there any progress?

@haomiemie commented on GitHub (Feb 26, 2025): Is there any progress?
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Feb 26, 2025):

Is there any progress?

NO @VincePotato

@wupeisheng commented on GitHub (Feb 26, 2025): > Is there any progress? NO @VincePotato
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@backrunner commented on GitHub (Mar 3, 2025):

Really need this feature, this UX is really annoyed

@backrunner commented on GitHub (Mar 3, 2025): Really need this feature, this UX is really annoyed
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@gizousa commented on GitHub (Mar 3, 2025):

Any update?

@gizousa commented on GitHub (Mar 3, 2025): Any update?
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@branchzero commented on GitHub (Mar 7, 2025):

Need this feature too, when we pass inputs(like user's token) via querystring, it(token) will be displayed at starter and user need click start chat again, UX seems strange on this case.

@branchzero commented on GitHub (Mar 7, 2025): Need this feature too, when we pass inputs(like user's token) via querystring, it(token) will be displayed at starter and user need click start chat again, UX seems strange on this case.
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@lsj19830812 commented on GitHub (Mar 11, 2025):

Plz, anyone has some way to skip this page?

@lsj19830812 commented on GitHub (Mar 11, 2025): Plz, anyone has some way to skip this page?
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@vlameiras commented on GitHub (Mar 11, 2025):

I haven't found a way to do it, so I wrote my own widget and connected it directly to the API.

@vlameiras commented on GitHub (Mar 11, 2025): I haven't found a way to do it, so I wrote my own widget and connected it directly to the API.
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 12, 2025):

See v1.0.1

Image

@crazywoola commented on GitHub (Mar 12, 2025): See v1.0.1 ![Image](https://github.com/user-attachments/assets/9186cdc0-76d2-4112-b8c7-b53f5f3877ec)
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Mar 13, 2025):

See v1.0.1

Image

Need this feature too, when we pass inputs(like user's token) via querystring, it(token) will be displayed at starter and user need click start chat again, UX seems strange on this case.

@crazywoola How can we skip it? Can't find the relevant documents

@dashing9527 commented on GitHub (Mar 13, 2025): > See v1.0.1 > > ![Image](https://github.com/user-attachments/assets/9186cdc0-76d2-4112-b8c7-b53f5f3877ec) > Need this feature too, when we pass inputs(like user's token) via querystring, it(token) will be displayed at starter and user need click start chat again, UX seems strange on this case. @crazywoola How can we skip it? Can't find the relevant documents
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 13, 2025):

@dashing9527 Sorry, we do not have plan to skip this.

@crazywoola commented on GitHub (Mar 13, 2025): @dashing9527 Sorry, we do not have plan to skip this.
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Mar 13, 2025):

抱歉，我们没有计划跳过这个。
@crazywoola
This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters

@dashing9527 commented on GitHub (Mar 13, 2025): > 抱歉，我们没有计划跳过这个。 @crazywoola This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Mar 13, 2025):

It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set

@wupeisheng commented on GitHub (Mar 13, 2025): It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set
yindo commented 2026-02-21 18:11:19 -05:00
Author
Owner
Copy Link
Copy Source

@wupeisheng commented on GitHub (Mar 13, 2025):

抱歉，我们没有计划跳过这个。
@crazywoola
This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters

It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set

@wupeisheng commented on GitHub (Mar 13, 2025): > > 抱歉，我们没有计划跳过这个。 > > [@crazywoola](https://github.com/crazywoola) > > This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set
yindo commented 2026-02-21 18:11:20 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Mar 13, 2025):

Sorry, we do not have plan to skip this.
@crazywoola
This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters

It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set

@wupeisheng Yes, I know, but in embedding my own business system, I also need to pass parameters. All I know so far is that parameters are passed in through difyChatbotConfig.inputs and then received in workflow, but I don't need to pop up the user, For example, the user does not understand the token, and the current situation is to show the user the default value I fill in. Thank you for your answer. We hope to open a parameter for us to use whether to display the input parameter popup window.

window.difyChatbotConfig = {
  token: 'NsbGX4y1mSmed1Fe',
  baseUrl: 'https://ai.jubocloud.com',
  inputs: {
   accessToken: 'Bearer **************************'
  },
 }

@dashing9527 commented on GitHub (Mar 13, 2025): > > > Sorry, we do not have plan to skip this. > > > [@crazywoola](https://github.com/crazywoola) > > > This is very strange, open to users generally need to do authentication with the business system, embedded in the business system after passing the token, in workflow to verify the token, this situation shows that the user also point to determine is meaningless, hope to be able to set whether the hidden parameters > > It has been verified and resolved in version 1.0.1. It will automatically open this dialog box based on whether the preceding dialogue content is set @wupeisheng Yes, I know, but in embedding my own business system, I also need to pass parameters. All I know so far is that parameters are passed in through difyChatbotConfig.inputs and then received in workflow, but I don't need to pop up the user, For example, the user does not understand the token, and the current situation is to show the user the default value I fill in. Thank you for your answer. We hope to open a parameter for us to use whether to display the input parameter popup window. ``` window.difyChatbotConfig = { token: 'NsbGX4y1mSmed1Fe', baseUrl: 'https://ai.jubocloud.com', inputs: { accessToken: 'Bearer **************************' }, } ``` ![](https://jubo-mall.oss-cn-hangzhou.aliyuncs.com/test-flow.png)
yindo commented 2026-02-21 18:11:20 -05:00
Author
Owner
Copy Link
Copy Source

@branchzero commented on GitHub (Mar 15, 2025):

@dashing9527 We made some changes based on (https://github.com/marsDes/dify-conversation), because official conversation seems not up to date.(https://github.com/langgenius/webapp-conversation). All you need to do is run another
fe container to serve the chat web.
You can modify app/components/chat-with-history/config-panel/form.tsx to get it done when loading this components(by use handleNewConversationInputsChange to load querystring's data and then use handleStartChat to start chat), may it helps you.

@branchzero commented on GitHub (Mar 15, 2025): @dashing9527 We made some changes based on (https://github.com/marsDes/dify-conversation), because official conversation seems not up to date.(https://github.com/langgenius/webapp-conversation). All you need to do is run another fe container to serve the chat web. You can modify `app/components/chat-with-history/config-panel/form.tsx` to get it done when loading this components(by use `handleNewConversationInputsChange` to load querystring's data and then use `handleStartChat` to start chat), may it helps you.
yindo commented 2026-02-21 18:11:20 -05:00
Author
Owner
Copy Link
Copy Source

@dashing9527 commented on GitHub (Mar 18, 2025):

@dashing9527 We made some changes based on (https://github.com/marsDes/dify-conversation), because official conversation seems not up to date.(https://github.com/langgenius/webapp-conversation). All you need to do is run another fe container to serve the chat web. You can modify to get it done when loading this components(by use to load querystring's data and then use to start chat), may it helps you.app/components/chat-with-history/config-panel/form.tsx``handleNewConversationInputsChange``handleStartChat

@branchzero Can I see the example you wrote, please

@dashing9527 commented on GitHub (Mar 18, 2025): > [@dashing9527](https://github.com/dashing9527) We made some changes based on (https://github.com/marsDes/dify-conversation), because official conversation seems not up to date.(https://github.com/langgenius/webapp-conversation). All you need to do is run another fe container to serve the chat web. You can modify to get it done when loading this components(by use to load querystring's data and then use to start chat), may it helps you.`app/components/chat-with-history/config-panel/form.tsx``handleNewConversationInputsChange``handleStartChat` @branchzero Can I see the example you wrote, please
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#5502
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?