Why doesn't the /chat-messages API allow passes context messages as a list?

[jamie0725]

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).
• Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Hi, I am new to the platform, but while I look through the API documentation (as attached below), I notice that the user is not allowed to pass the context history on his own. The feature is important for customer support scenarios where the AI agent is not the only responder in the conversation (i.e., there might be a human agent and other business messages previously involved). This means that relying solely on the context history of the agent will not suffice to answer the user's question:

curl -X POST 'https://api.dify.ai/v1/chat-messages' \
--header 'Authorization: Bearer {api_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "inputs": {},
    "query": "What are the specs of the iPhone 13 Pro Max?",
    "response_mode": "streaming",
    "conversation_id": "",
    "user": "abc-123",
    "files": [
      {
        "type": "image",
        "transfer_method": "remote_url"
        "url": "https://cloud.dify.ai/logo/logo-site.png"
      }
    ]
}'

2. Describe the feature you'd like to see

I'd like to have the query field to support list conversations to carry the context (similar to ChatGPT messages), and in this case not using the context information of the dify platform.

3. How will this feature improve your workflow or experience?

a must for customer support, if no workaround is available.

4. Additional context or comments

No response

5. Can you help us with this feature?

• I am interested in contributing to this feature.

[crazywoola]

Dify provide apis to the whole application. It's not a proxy to other api like OpenAI itself.

[jamie0725]

Yes I understand, but looking at my scenario (which could be quite common), I still think that allowing the user to pass in the context history (at least the user and assistant messages) would be an important feature.

[jamie0725]

Or does the context module have an API that allows the user to modify, which could be a workaround.

[MrOrz]

Despite the endpoint name being /chat-messages, the way this API works is more similar to OpenAI Assistant API, which manages the history of a thread all by itself and does not allow editing of the history.

A question that may arise after introducing the feature that specifies or modifies history would be: what should "Logs and Annotations" tab show after the user provides a new chat history? Having a good answer to that question may be a good start towards the actual implementation of such feature.

[glacierck]

Despite the endpoint name being /chat-messages, the way this API works is more similar to OpenAI Assistant API, which manages the history of a thread all by itself and does not allow editing of the history.

A question that may arise after introducing the feature that specifies or modifies history would be: what should "Logs and Annotations" tab show after the user provides a new chat history? Having a good answer to that question may be a good start towards the actual implementation of such feature.

/chat-messages no longer supports modifying historical messages!They canceled 'parent_message_id'!!!