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

Edit Agent Instructions/Prompt After Starting Multiple Conversations #6705

New Issue
Closed
opened 2026-02-21 18:16:56 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:16:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @ketchalegend on GitHub (Nov 12, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Steps to reproduce

At the moment, when I start multiple conversations using the API and later edit the agent prompt, it is not updated in the individual conversations. For example, if before the conversation starts with the prompt "You're selling books", I start a conversation and then later on, while I'm in the conversation using the API endpoint, I go back in the instruction and change the prompt to "You're selling shoes". The conversation is not updated to use the new prompt.

The conversation doesn't know about a new prompt; it still uses the old prompt.

Steps to Reproduce

Start multiple conversations using the API with an initial prompt (e.g., "You're selling books").
Edit the agent prompt to a new prompt (e.g., "You're selling shoes") while the conversations are active.
Observe if the conversations use the new prompt.

✔️ Expected Behavior

Active and old conversations should use the updated prompt.

Is there a possibilty to make it apply to older conversations too? Cause that means i will have to delete all users conversations everytime i make changes to the prompt, which will ofcourse mean that the context is gone.?

❌ Actual Behavior

Active and old conversations continue to use the old prompt, not reflecting the updated instructions.

Originally created by @ketchalegend on GitHub (Nov 12, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 0.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ### Steps to reproduce At the moment, when I start multiple conversations using the API and later edit the agent prompt, it is not updated in the individual conversations. For example, if before the conversation starts with the prompt "You're selling books", I start a conversation and then later on, while I'm in the conversation using the API endpoint, I go back in the instruction and change the prompt to "You're selling shoes". The conversation is not updated to use the new prompt. The conversation doesn't know about a new prompt; it still uses the old prompt. ### Steps to Reproduce Start multiple conversations using the API with an initial prompt (e.g., "You're selling books"). Edit the agent prompt to a new prompt (e.g., "You're selling shoes") while the conversations are active. Observe if the conversations use the new prompt. ### ✔️ Expected Behavior Active and old conversations should use the updated prompt. Is there a possibilty to make it apply to older conversations too? Cause that means i will have to delete all users conversations everytime i make changes to the prompt, which will ofcourse mean that the context is gone.? ### ❌ Actual Behavior Active and old conversations continue to use the old prompt, not reflecting the updated instructions.
yindo added the 🐞 bug label 2026-02-21 18:16:56 -05:00
yindo closed this issue 2026-02-21 18:16:56 -05:00
yindo commented 2026-02-21 18:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 12, 2024):

This is an expected behavior, you can not update the instructions nor the input parameters, everything in the started conversation is a snapshot of the configuration.

We had a discussion internally before, and we decide to remain current situation, also, there is a pr for this and linked several duplicated discussions as well. https://github.com/langgenius/dify/pull/7955

@crazywoola commented on GitHub (Nov 12, 2024): This is an expected behavior, you can not update the instructions nor the input parameters, everything in the started conversation is a snapshot of the configuration. We had a discussion internally before, and we decide to remain current situation, also, there is a pr for this and linked several duplicated discussions as well. https://github.com/langgenius/dify/pull/7955
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 🐞 bug
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#6705
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?