Feedback

Many businesses want more connectors to software they already use. Suggestions: Websites (see that this is coming soon) Slack Google Drive Github Microsoft Teams Also Zapier to include a lot more.

Hello Dify Community, I am facing a challenge that I believe others may also encounter: the user experience (UX) of Dify Chat is not as engaging or feature-rich as other tools like ChatGPT, which affects user adoption within my company. Here are the features I'd like to see implemented to address this issue: Is this request related to a challenge you are facing? Yes, the current UX limitations of Dify Chat lead users to prefer other tools with more comprehensive features. What is the feature you'd like to see? I propose several enhancements for Dify Chat: The ability to regenerate responses similar to ChatGPT. Editing my own messages to prompt new responses from the LLM. Sharing chat sessions with others. Enabling web search capabilities within chats. Preventing automatic scrolling down when reading previous parts of the conversation. Introducing a dark mode for better usability at night or in low-light environments. An option to toggle full-width UI for better use of browser space. These features are inspired by existing tools such as https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web . How will this feature improve your workflow/experience? Enhancing Dify Chat will make interactions more enjoyable and increase user engagement. It's expected that these improvements will lead to higher usage numbers for my Dify apps. Additional Context or Comments Taking inspiration from existing tools can help us develop new features that meet user expectations and improve overall satisfaction with Dify Chat. Can you help with this feature? My company can assist with UI/UX design efforts. Additionally, I have prepared a script that adds dark mode support to the entire Dify platform; it requires minor adjustments before sharing. I am also willing to contribute through concept discussions on Discord, including voice chat and pair programming sessions. Furthermore, I'll participate in testing phases and provide feedback on functionality prior to release. Thank you for considering these suggestions. I believe they will significantly enhance the usability and appeal of Dify Apps and look forward to

Currently, a maximum of 15 items are displayed per page, which is not making full use of the screen. It is recommended to support the selection of the maximum number of items to be displayed per page

Hello Dify Community, I'm reaching out to suggest a new feature that addresses a significant challenge in user experience when working with Dify apps, particularly during code generation tasks. Is this request related to a challenge you are facing? Yes, the issue arises when generating large content that hits the maximum output token limit, causing the generation to abruptly stop, sometimes in the middle of a code block. Users can send "continue" to get a complete result but this results in an incomplete output which cannot be easily used or copied as intended. What is the feature you'd like to see? I propose two enhancements: A "continue generation" button that appears when content generation reaches the max token limit. This button should allow users to seamlessly continue generating content within the same message. - The button text should be internationalized and customizable within Dify Studio. An optional auto-continue feature that can be enabled to automatically extend content until a complete response is generated without hitting the token limit. How will this feature improve your workflow / experience? The implementation of these features would enable smoother and uninterrupted content creation, particularly beneficial for generating extensive outputs such as long-form articles or complete code blocks without manual intervention. Additional Context or Comments This functionality is available in ChatGPT and there are open-source tools for the "auto continue" feature, indicating a clear demand for such capabilities within generative AI applications like those built on Dify. While I am not able to contribute directly to developing this feature through coding or financial sponsorship, I believe its addition would greatly enhance user satisfaction and align with existing expectations set by other AI platforms. I look forward to hearing what others think about this idea and seeing how we can make using Dify apps an even better experience!

RT，先给DIFY点个赞，越用越好用 希望的功能： 希望能从”日志和标注“中, 一键填写编排中的用户输入，方便调试优化PROMPT 如果能支持从”日志和标注“中挑选历史请求，来用于批量回顾性测试就更好了，类似优化PROMPT之后的”回测“ 体验问题： 现在如果发现”日志与标注“中的问题CASE，需要手动将每个用户输入变量拷贝至编排页面调试 甚至还存在拷贝过去吞换行的问题，如果能一键调试就好办很多，有点像SD-webui通过生成的图片meta-info一键恢复图片生成prompt和配置

Just spent a bunch of time setting up a bot in the studio. Left the page to setup the knowledge and came back and everything was gone and reset to default?! Tried putting in some more content and again and it was gone. Do I use publish to save? This seems counterintuitive as I want to save not publish. Perhaps enable auto-save. But not sure what to do now.

Very confused, tried going to help to try to find a way to contact to send feedback and was not able to find any information. The feedback button on the menu is not super clear.

When doing changes to prompts, adding functions etc. during orchestrating of an AI assistant, it can be frustrating to forget to hit the "publish" button before moving away from the page. I suggest a implementation of a "Do you want to save" before navigation away. So users don't loose work they have done.

Hello Dify Community, I'd like to propose a feature that addresses a challenge I've encountered: selecting the correct model for Dify apps when faced with non-descriptive deployment names from model providers. Is this request related to a challenge you are facing? Yes, the challenge is the difficulty in identifying the correct model due to generic or non-descriptive deployment names that are carried over from model providers like Azure to Dify. What is the feature you'd like to see? I propose adding an optional field called displayName to the model setup form in Dify. This field would allow users to enter a more descriptive and user-friendly name for the model. If a displayName is provided, it should be displayed in the UI select inputs instead of the model name. If not provided, the model name would be used as a fallback. How will this feature improve your workflow / experience? This feature will significantly enhance the model selection process by allowing me—and potentially other users—to quickly identify the right model for our Dify apps. It also enables the creation of model aliases tailored to specific use cases, such as "coding assistant model" for coding-related tasks, which simplifies the selection process for non-experts. Additional Context or Comments The UI should prioritize displaying the displayName over the model name in all selection interfaces within Dify when both are available. This will ensure a user-friendly and efficient model selection experience. Can you help with this feature? I am open to assisting with testing and providing feedback to ensure the feature is implemented effectively and meets user needs. I believe this feature will be a valuable addition to Dify, enhancing usability and reducing confusion during model selection. I look forward to the community's thoughts and feedback on this suggestion.

Hello Dify Community, I'm thrilled to propose an extension to the Dify app's variables feature: the Advanced Variable Instructions . This feature will empower users to define multiple instruction blocks and combine them based on conditions, creating more dynamic and responsive interactions. Why Advanced Variable Instructions? Conditional Logic: Users can define blocks of instructions that are executed based on the presence or value of specific variables. This allows for more personalized and context-aware conversation flows. Complex Scenarios: With the ability to use conditions such as greater than, less than, or equal to, users can build advanced logic into their Dify apps, enabling them to handle a wide range of user inputs and scenarios. Enhanced User Experience: By tailoring the conversation flow based on the user's inputs, Dify apps can provide a more intuitive and personalized experience, leading to higher user engagement. Currently it requires prompt engineering to handle optional variables in the instructions because when the value is not provided, the LLM might not understand the instruction. Adding a instruction block only when a variable is set, makes it so much easier. Feature Enhancements: Expanded Variable Types: In addition to the existing variables like selects, short text inputs, and text paragraphs, we will introduce number and boolean variables to allow for easier definition of conditions. Dynamic Enabling of Features: Users can specify conditions for enabling or disabling advanced features such as RAG (Retrieval Augmented Generation) based on the values or presence of specific variables, providing more granular control over the functionality of their Dify apps. Incorporation into Expert Mode: To maintain simplicity for regular users, this extended functionality will be incorporated into the expert mode of the Dify app's prompt engineering section, providing a seamless transition for users who are ready to explore and implement more advanced logic. I look forward to hearing your thoughts and feedback on this revised feature suggestion! Let's build a more powerful and versatile Dify app together.