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

Please support for an interface similar to OpenAI's multi-turn dialogue #5033

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

Originally created by @bswaterb on GitHub (Aug 14, 2024).

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.

When calling OpenAI's Chat-Message API, you can pass session information using the "messages" parameter, allowing me to manually construct a historical context to include, such as:

curl https://api.openai.com/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -d '{
     "model": "gpt-4o-mini",
     "messages": [{"role": "user", "content": "Here is the content"}, {"role": "assistant", "content": "OK"}, {"role": "user", "content": "what are we talking about?"}],
     "temperature": 0.7
   }'

However, in the external API interface or Workflow provided by Dify, it is not possible to complete tasks based on context provided externally; you can only initiate a conversation and maintain the context of that conversation through Dify itself.

Therefore, I request that Dify support an interface that allows users to construct their own historical context for conversation generation.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @bswaterb on GitHub (Aug 14, 2024). ### 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. When calling OpenAI's Chat-Message API, you can pass session information using the "messages" parameter, allowing me to manually construct a historical context to include, such as: ``` curl https://api.openai.com/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $OPENAI_API_KEY" \ -d '{ "model": "gpt-4o-mini", "messages": [{"role": "user", "content": "Here is the content"}, {"role": "assistant", "content": "OK"}, {"role": "user", "content": "what are we talking about?"}], "temperature": 0.7 }' ``` However, in the external API interface or Workflow provided by Dify, it is not possible to complete tasks based on context provided externally; you can only initiate a conversation and maintain the context of that conversation through Dify itself. Therefore, I request that Dify support an interface that allows users to construct their own historical context for conversation generation. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:09:06 -05:00
yindo closed this issue 2026-02-21 18:09:06 -05:00
yindo commented 2026-02-21 18:09:06 -05:00
Author
Owner
Copy Link
Copy Source

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

You should use Chatflow or Agent. Workflow is designed as a one-off task.

@crazywoola commented on GitHub (Aug 14, 2024): You should use Chatflow or Agent. Workflow is designed as a one-off task.
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 💪 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#5033
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?