I deployed Dify using Docker. How can I configure it so that each visit opens a new conversation instead of loading the previous one? #28221
Replies: 1 comment 8 replies
-
|
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 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 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 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 |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Self Checks
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?
Beta Was this translation helpful? Give feedback.
All reactions