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

Implement Conversation State Management and Menu-Based Navigation in Dify Chatbot Orchestration Tool #4929

New Issue
Closed
opened 2026-02-21 18:08:39 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:08:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @Delgerskhn on GitHub (Aug 7, 2024).

Originally assigned to: @VincePotato on GitHub.

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 would like to request a feature enhancement for the Dify chatbot orchestration tool. Currently, the tool follows a linear workflow that doesn't persist the conversation state, requiring the LLM to process each step from the beginning for every user query. This can lead to misinterpretation of user intentions and incorrect responses.

Proposed Feature:
Implement a conversation state management feature that allows for menu-based navigation. This would involve:
Menu-Based Navigation:

  • Users can navigate through a series of menus to narrow down their query.
  • Each menu and submenu will have specific actions that the user can perform.

State Persistence:

  • Maintain the state of the conversation so that users can continue from where they left off.
  • Provide options like "Go back to previous menu" and "Go to start" to manage the conversation flow easily.

Action Declaration:

  • In each leaf state, declare specific actions that the user can perform.
  • Example actions: View contact info, get aid, learn about branches, etc.

Benefits:

  • Improves user experience by allowing easier navigation and interaction.
  • Reduces the likelihood of incorrect responses by narrowing down user queries through menus.
  • Enhances the LLM's understanding of user intentions by maintaining context and state.
  • I believe this feature will significantly enhance the capabilities of the Dify orchestration tool and improve the overall user experience.

Thank you for considering this feature request.

Example Usage:

  1. User starts at the ROOT menu.
  2. User selects "Contact Support" and is taken to the CONTACT_SUPPORT menu.
  3. User can then choose "Branches" to get information about branches or "Contact Info" to view contact details.
  4. At any point, the user can choose to go back to the previous menu or return to the start.

2. Additional context or comments

I have provided an example of how I manage state in my messenger chatbot. This could serve as a reference for implementing this feature in Dify.

Example state management state machine I use in messenger chatbot:

export const states = {
  ROOT: "ROOT",
  CONTACT_SUPPORT: "CONTACT_SUPPORT",
  CONTACT_INFO: "CONTACT_INFO",
  ABOUT_US: "ABOUT_US",
  BRANCHES: "BRANCHES",
  BRANCH_INFO: "BRANCH_INFO",
  GET_AID: "GET_AID"
};

export const transitions = {
  [states.ROOT]: [states.CONTACT_SUPPORT, states.ABOUT_US, states.GET_AID],
  [states.ABOUT_US]: [states.ROOT],
  [states.CONTACT_SUPPORT]: [states.BRANCHES, states.CONTACT_INFO, states.ROOT],
  [states.BRANCHES]: [states.BRANCH_INFO, states.ROOT],
  [states.BRANCH_INFO]: [states.ROOT, states.BRANCHES],
  [states.GET_AID]: [states.ROOT]
};

export const messages = {
  [states.ROOT]: {
    attachment: {
      type: "template",
      payload: {
        template_type: "button",
        text: "Сайн байна уу? Хууль зүйн туслалцааны төвтэй холбогдлоо. Та доорх цэснээс сонгоно уу.",
        buttons: [
          {
            type: "postback",
            title: "Холбоо барих",
            payload: states.CONTACT_SUPPORT
          },
          {
            type: "postback",
            title: "Үйлчилгээ, үйл ажиллагаа",
            payload: states.ABOUT_US
          },
          {
            type: "postback",
            title: "Хууль зүйн зөвлөгөө",
            payload: states.GET_AID
          }
        ]
      }
    }
  },
  [states.ABOUT_US]: {
    attachment: {
      type: "template",
      payload: {
        template_type: "button",
        text: "Та лавлахыг хүссэн асуултаа асууна уу?",
        buttons: [
          {
            type: "postback",
            title: "Буцах",
            payload: "BACK"
          }
        ]
      }
    }
  }
};


import { callSendAPI } from "./callSendApi"; // Adjust the path as needed
import { messages, states, transitions } from "./chat_state";

export const stateMachine = {
  userStates: {},

  getState(userId) {
    return this.userStates[userId] || states.ROOT;
  },

  setState(userId, newState) {
    if (transitions[this.getState(userId)].includes(newState)) {
      this.userStates[userId] = newState;
    } else {
      console.error(
        `Invalid transition from ${this.getState(userId)} to ${newState}`
      );
    }
  },

  /**
   * Presents options to the user based on their current state.
   *
   * @param {string} userId - The ID of the user.
   * @return {Promise<void>} A promise that resolves when the options are presented.
   */
  async presentOptions(userId) {
    const currentState = this.getState(userId);
    console.log("state>", currentState);
    const response = messages[currentState];

    await callSendAPI(userId, response);
  }
};

// Handle Postback
export async function handlePostback(senderPsid, receivedPostback) {
  const payload = receivedPostback.payload;
  stateMachine.setState(senderPsid, payload);
  await stateMachine.presentOptions(senderPsid);
}

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Delgerskhn on GitHub (Aug 7, 2024). Originally assigned to: @VincePotato on GitHub. ### 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 would like to request a feature enhancement for the Dify chatbot orchestration tool. Currently, the tool follows a linear workflow that doesn't persist the conversation state, requiring the LLM to process each step from the beginning for every user query. This can lead to misinterpretation of user intentions and incorrect responses. **Proposed Feature:** Implement a conversation state management feature that allows for menu-based navigation. This would involve: Menu-Based Navigation: - Users can navigate through a series of menus to narrow down their query. - Each menu and submenu will have specific actions that the user can perform. **State Persistence:** - Maintain the state of the conversation so that users can continue from where they left off. - Provide options like "Go back to previous menu" and "Go to start" to manage the conversation flow easily. **Action Declaration:** - In each leaf state, declare specific actions that the user can perform. - Example actions: View contact info, get aid, learn about branches, etc. **Benefits:** - Improves user experience by allowing easier navigation and interaction. - Reduces the likelihood of incorrect responses by narrowing down user queries through menus. - Enhances the LLM's understanding of user intentions by maintaining context and state. - I believe this feature will significantly enhance the capabilities of the Dify orchestration tool and improve the overall user experience. Thank you for considering this feature request. Example Usage: 1. User starts at the ROOT menu. 2. User selects "Contact Support" and is taken to the CONTACT_SUPPORT menu. 3. User can then choose "Branches" to get information about branches or "Contact Info" to view contact details. 4. At any point, the user can choose to go back to the previous menu or return to the start. ### 2. Additional context or comments I have provided an example of how I manage state in my messenger chatbot. This could serve as a reference for implementing this feature in Dify. Example state management state machine I use in messenger chatbot: ``` export const states = { ROOT: "ROOT", CONTACT_SUPPORT: "CONTACT_SUPPORT", CONTACT_INFO: "CONTACT_INFO", ABOUT_US: "ABOUT_US", BRANCHES: "BRANCHES", BRANCH_INFO: "BRANCH_INFO", GET_AID: "GET_AID" }; export const transitions = { [states.ROOT]: [states.CONTACT_SUPPORT, states.ABOUT_US, states.GET_AID], [states.ABOUT_US]: [states.ROOT], [states.CONTACT_SUPPORT]: [states.BRANCHES, states.CONTACT_INFO, states.ROOT], [states.BRANCHES]: [states.BRANCH_INFO, states.ROOT], [states.BRANCH_INFO]: [states.ROOT, states.BRANCHES], [states.GET_AID]: [states.ROOT] }; export const messages = { [states.ROOT]: { attachment: { type: "template", payload: { template_type: "button", text: "Сайн байна уу? Хууль зүйн туслалцааны төвтэй холбогдлоо. Та доорх цэснээс сонгоно уу.", buttons: [ { type: "postback", title: "Холбоо барих", payload: states.CONTACT_SUPPORT }, { type: "postback", title: "Үйлчилгээ, үйл ажиллагаа", payload: states.ABOUT_US }, { type: "postback", title: "Хууль зүйн зөвлөгөө", payload: states.GET_AID } ] } } }, [states.ABOUT_US]: { attachment: { type: "template", payload: { template_type: "button", text: "Та лавлахыг хүссэн асуултаа асууна уу?", buttons: [ { type: "postback", title: "Буцах", payload: "BACK" } ] } } } }; import { callSendAPI } from "./callSendApi"; // Adjust the path as needed import { messages, states, transitions } from "./chat_state"; export const stateMachine = { userStates: {}, getState(userId) { return this.userStates[userId] || states.ROOT; }, setState(userId, newState) { if (transitions[this.getState(userId)].includes(newState)) { this.userStates[userId] = newState; } else { console.error( `Invalid transition from ${this.getState(userId)} to ${newState}` ); } }, /** * Presents options to the user based on their current state. * * @param {string} userId - The ID of the user. * @return {Promise<void>} A promise that resolves when the options are presented. */ async presentOptions(userId) { const currentState = this.getState(userId); console.log("state>", currentState); const response = messages[currentState]; await callSendAPI(userId, response); } }; // Handle Postback export async function handlePostback(senderPsid, receivedPostback) { const payload = receivedPostback.payload; stateMachine.setState(senderPsid, payload); await stateMachine.presentOptions(senderPsid); } ``` ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 18:08:39 -05:00
yindo closed this issue 2026-02-21 18:08:39 -05:00
yindo commented 2026-02-21 18:08:39 -05:00
Author
Owner
Copy Link
Copy Source

@Delgerskhn commented on GitHub (Aug 7, 2024):

Example messenger postback buttons that I use for state management.
Screenshot 2024-08-07 at 14 02 49
Also menu selection can be like this one used in telegram.
Screenshot 2024-08-07 at 14 03 45

@Delgerskhn commented on GitHub (Aug 7, 2024): Example messenger postback buttons that I use for state management. <img width="591" alt="Screenshot 2024-08-07 at 14 02 49" src="https://github.com/user-attachments/assets/0154851b-cfb6-4927-bda3-5640e00223b2"> Also menu selection can be like this one used in telegram. <img width="591" alt="Screenshot 2024-08-07 at 14 03 45" src="https://github.com/user-attachments/assets/50b46405-8f18-4ca4-9312-2b2729981395">
yindo commented 2026-02-21 18:08:39 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 13, 2024):

This sounds good and introduces a state machine, but it can be quite complicated to implement.

@crazywoola commented on GitHub (Aug 13, 2024): This sounds good and introduces a state machine, but it can be quite complicated to implement.
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 🌊 feat:workflow 💪 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#4929
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?