langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 13:05:55 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Automatically Enter "Conversation Opener" When Parameters Are Not Empty #12422

New Issue
Closed
opened 2026-02-21 19:07:20 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:07:20 -05:00
Owner
Copy Link
Copy Source

Originally created by @alienwaredream on GitHub (Apr 1, 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.

Description:
I've developed a chatflow application. The third - party system opens a link with variable values through embedded development (e.g., http://172.16.1.5/chatbot/BPXo1mzjte2bjdSd?jzkh=H4sIAM/s6WcC/zMyMLAEAF20Tt8EAAAA). Currently, every time the WEBUI is opened, users have to click the "start chat" button to enter the "Conversation Opener".
Current Situation:
When the third - party system opens the application link with parameters, users are required to manually click the "start chat" button to initiate the conversation. This extra step adds inconvenience to the user experience.
Expected Requirement:
I propose adding a feature where if the parameter values in the URL are not empty, the application should directly enter the "Conversation Opener" interface without the need for users to click the "start chat" button. This improvement would significantly streamline the user operation process and enhance the overall user experience.
Suggested Implementation Steps:
Add a check mechanism in the application to detect whether the parameter values in the URL are empty.
If the parameter values are not empty, bypass the "start chat" button click requirement and directly load the "Conversation Opener" interface.
Please review this issue and let me know if there are any questions or concerns. Thank you!

Image

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @alienwaredream on GitHub (Apr 1, 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. Description: I've developed a chatflow application. The third - party system opens a link with variable values through embedded development (e.g., http://172.16.1.5/chatbot/BPXo1mzjte2bjdSd?jzkh=H4sIAM/s6WcC/zMyMLAEAF20Tt8EAAAA). Currently, every time the WEBUI is opened, users have to click the "start chat" button to enter the "Conversation Opener". Current Situation: When the third - party system opens the application link with parameters, users are required to manually click the "start chat" button to initiate the conversation. This extra step adds inconvenience to the user experience. Expected Requirement: I propose adding a feature where if the parameter values in the URL are not empty, the application should directly enter the "Conversation Opener" interface without the need for users to click the "start chat" button. This improvement would significantly streamline the user operation process and enhance the overall user experience. Suggested Implementation Steps: Add a check mechanism in the application to detect whether the parameter values in the URL are empty. If the parameter values are not empty, bypass the "start chat" button click requirement and directly load the "Conversation Opener" interface. Please review this issue and let me know if there are any questions or concerns. Thank you! ![Image](https://github.com/user-attachments/assets/4718bb90-7e8b-41b2-9d1b-f6fce85b1a1e) ### 2. Additional context or comments _No response_ ### 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:07:20 -05:00
yindo closed this issue 2026-02-21 19:07:20 -05:00
yindo commented 2026-02-21 19:07:20 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary:

  • Enhancement proposed to improve chatflow user experience.
  • Automatically enter "Conversation Opener" with non-empty URL parameters.
  • Aims to remove the need for a manual "start chat" button click.
  • No further activity or comments have been made on this issue.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no response, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (May 2, 2025): Hi, @alienwaredream. 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:** - Enhancement proposed to improve chatflow user experience. - Automatically enter "Conversation Opener" with non-empty URL parameters. - Aims to remove the need for a manual "start chat" button click. - No further activity or comments have been made on this issue. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no response, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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#12422
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?