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

Add OpenClaw Tool/Function Calling Support in Chatflow #22108

New Issue
Open
opened 2026-02-21 20:15:48 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:15:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @JAVA-LW on GitHub (Feb 5, 2026).

Originally assigned to: @JAVA-LW on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 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.

I attempted to integrate Dify as a model provider into OpenClaw (see openclaw/openclaw#7900), but encountered a critical compatibility issue: Dify's Chatflow cannot properly handle or execute OpenClaw-style tool callbacks.
When using Dify as the LLM backend via API, tool calls from OpenClaw are either not recognized by Dify's LLM node, or not executed properly in the Chatflow workflow. This prevents Dify from serving as a model provider for OpenClaw users who rely on standardized tool calling across different LLM backends.
I believe this integration would create valuable synergy between Dify's visual workflow capabilities and OpenClaw's standardized tool ecosystem, enabling more deployment flexibility for users who want to combine both platforms.

2. Additional context or comments

I'm willing to contribute this feature myself. Could you advise on:
Where in the codebase should tool calling protocol adaptation be implemented?
Is there an existing plugin/extension mechanism for custom tool calling formats?
Should this be implemented as a new node type, an enhancement to the existing LLM node, or a middleware layer in the API?
Environment:
Dify version: latest/main
Integration target: OpenClaw LLM gateway

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @JAVA-LW on GitHub (Feb 5, 2026). Originally assigned to: @JAVA-LW on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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. I attempted to integrate Dify as a model provider into OpenClaw (see [openclaw/openclaw#7900](https://github.com/openclaw/openclaw/pull/7900)), but encountered a critical compatibility issue: Dify's Chatflow cannot properly handle or execute OpenClaw-style tool callbacks. When using Dify as the LLM backend via API, tool calls from OpenClaw are either not recognized by Dify's LLM node, or not executed properly in the Chatflow workflow. This prevents Dify from serving as a model provider for OpenClaw users who rely on standardized tool calling across different LLM backends. I believe this integration would create valuable synergy between Dify's visual workflow capabilities and OpenClaw's standardized tool ecosystem, enabling more deployment flexibility for users who want to combine both platforms. ### 2. Additional context or comments I'm willing to contribute this feature myself. Could you advise on: Where in the codebase should tool calling protocol adaptation be implemented? Is there an existing plugin/extension mechanism for custom tool calling formats? Should this be implemented as a new node type, an enhancement to the existing LLM node, or a middleware layer in the API? Environment: Dify version: latest/main Integration target: OpenClaw LLM gateway ### 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 20:15:48 -05:00
yindo commented 2026-02-21 20:15:49 -05:00
Author
Owner
Copy Link
Copy Source

@JAVA-LW commented on GitHub (Feb 9, 2026):

I have already implemented it, how about I merge it directly into the main branch? Should we merge it into the refactor/skill-bundler first.
@crazywoola

@JAVA-LW commented on GitHub (Feb 9, 2026): I have already implemented it, how about I merge it directly into the main branch? Should we merge it into the refactor/skill-bundler first. @crazywoola
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#22108
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?