I deployed Dify using Docker. How can I configure it so that each visit opens a new conversation instead of loading the previous one?

[17600120049]

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.

Content

I deployed Dify using Docker. How can I configure it so that each visit opens a new conversation instead of loading the previous one?

[dosubot[bot]]

Hi @17600120049! I'm Dosu and I’m helping the dify team.

There isn't a built-in configuration or environment variable in Dify to force a new conversation on each visit. Dify keeps conversation state in localStorage, keyed by userId and appId, so it loads previous conversations for the same user by design.

If you're embedding Dify via iframe, you can start a new conversation each time by generating a unique userId for every load and passing it as the sys.user_id URL parameter (gzip, base64, and URI encoded). This will isolate sessions and prevent previous chat history from appearing, but it also hides the conversation history list for that user details.

If you want to keep the history list but always start a new conversation, you would need to programmatically trigger a new conversation in the frontend (for example, by calling the handleNewConversation function in the embedded Chatflow component), but this requires custom scripting and is not available as a simple config reference.

For the standard web UI, there is currently no config to force a new conversation per visit. You would need to customize the frontend to clear the relevant localStorage keys (like CONVERSATION_ID_INFO) or patch the logic that loads previous conversations reference. This would require code changes.

In summary: no config exists for this, but you can achieve the effect with custom scripting or by manipulating user/session IDs, depending on your deployment and embedding method.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[dosubot[bot]]

To always open a new conversation by default, you need to modify the frontend code to call the handleNewConversation function when the chat component mounts. This function is defined in web/app/components/base/chat/embedded-chatbot/hooks.tsx inside the useEmbeddedChatbot hook. It resets the conversation state and starts a new conversation, just like the "reset chat" button does in the UI.

To implement this, add a useEffect in the main chat component (where useEmbeddedChatbot is used) that calls handleNewConversation on mount. This will ensure every visit starts fresh, ignoring any previous conversation stored in localStorage. You can see the function definition and related logic here: handleNewConversation in hooks.tsx.

If you want to keep the conversation history list visible, keep the same userId but trigger handleNewConversation programmatically on each load. If you want a completely clean state (no history), you can also clear the relevant localStorage keys before mounting the chat component.

There is no config or environment variable for this—code modification is required.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[17600120049]

Thank you for the reply

[17600120049]

I tried making this change, but it doesn't seem to have taken effect.

[dosubot[bot]]

The reason your change didn't take effect is likely because handleNewConversation() was called before userId and conversationId were set from the URL or global store. In Dify's frontend, these states are initialized asynchronously—so if you trigger handleNewConversation too early, the reset logic uses stale or default values, and the previous conversation state can persist or be restored by later effects or context syncs details.

To reliably start a new conversation on each visit, call handleNewConversation only after userId and conversationId are set. You can do this by adding a useEffect like:

useEffect(() => {
  if (userId !== undefined && conversationId !== undefined) {
    handleNewConversation();
  }
}, [userId, conversationId]);

This ensures the reset happens after those states are initialized. If you want a truly clean state, also consider clearing the relevant localStorage keys before mounting the chat component.

Let me know if you want help with a specific code snippet or integration!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[bitifi2019]

@dosu please offer a specific code snippet or integration! thanks