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

LLM based inference of Workflow node parameters when they are not explicitly defined. #3045

New Issue
Closed
opened 2026-02-21 17:53:06 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:53:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @bekhruz-ti on GitHub (May 8, 2024).

Originally assigned to: @VincePotato on GitHub.

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?

Issue with Dify's ChatFlow feature. I initiated some nodes that required certain parameters. ChatFlow allowed me to initiate a run from a message in the chatbox. The message contained all necessary parameters for the intermediate nodes to execute successfully, but these parameter values were not inferred, causing the chatflow run to fail with an error.

2. Describe the feature you'd like to see

I'd like a mechanism similar to Agent Behavior, where when a tool parameter is specified as form: llm in the schema, the system automatically fills in the parameter value based on the user's message. This would eliminate the need for the user to prefill the parameter value in the chatflow tool node. Without this feature, the capabilities offered by ChatFlow are very similar to those of WorkFlow, and there's no significant differentiation.

For improved inference, it would be beneficial to provide the entire chat history at the time of parameter inference.

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

I can interact with my workflow in the same way I interact with agents.
I won't have to fill out forms.
I'll be able to publish more reusable ChatFlows. As, I can specify the tool parameters during execution time instead of at chatflow creation time, it will enable more generic use cases for each published ChatFlow.

4. Additional context or comments

This inferencing capability should be added to every built-in tool, likely within the class ToolNode after tool configurations describing the schema have been fetched. If a parameter value is empty, user input and preferably chat history should be passed to an LLM call along with the input schema fetched from the tool.yml file. The LLM should then be able to fill in the parameters passed into the tool, just like Agents currently do.

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @bekhruz-ti on GitHub (May 8, 2024). Originally assigned to: @VincePotato on GitHub. ### 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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Issue with Dify's ChatFlow feature. I initiated some nodes that required certain parameters. ChatFlow allowed me to initiate a run from a message in the chatbox. The message contained all necessary parameters for the intermediate nodes to execute successfully, but these parameter values were not inferred, causing the chatflow run to fail with an error. ### 2. Describe the feature you'd like to see I'd like a mechanism similar to Agent Behavior, where when a tool parameter is specified as `form: llm` in the schema, the system automatically fills in the parameter value based on the user's message. This would eliminate the need for the user to prefill the parameter value in the chatflow tool node. Without this feature, the capabilities offered by ChatFlow are very similar to those of WorkFlow, and there's no significant differentiation. For improved inference, it would be beneficial to provide the entire chat history at the time of parameter inference. ### 3. How will this feature improve your workflow or experience? I can interact with my workflow in the same way I interact with agents. I won't have to fill out forms. I'll be able to publish more reusable ChatFlows. As, I can specify the tool parameters during execution time instead of at chatflow creation time, it will enable more generic use cases for each published ChatFlow. ### 4. Additional context or comments This inferencing capability should be added to every built-in tool, likely within the class ToolNode after tool configurations describing the schema have been fetched. If a parameter value is empty, user input and preferably chat history should be passed to an LLM call along with the input schema fetched from the `tool.yml` file. The LLM should then be able to fill in the parameters passed into the tool, just like Agents currently do. ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:53:06 -05:00
yindo closed this issue 2026-02-21 17:53:06 -05:00
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#3045
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?