Adding tools or plugins to the agent module fails to function properly
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### 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] 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, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.
### Dify version
1.17.0、1.16.1
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
Add tools to the Agent's tool list.
1. The parameters of the tool cannot be set manually.
2. There is an issue with the model used in the tool. The process of "model -> save -> apply to agent" is ineffective.
### ✔️ Expected Behavior
Please make the configuration of the tool compatible so that it can be used normally.
### ❌ Actual Behavior
Add tools to the Agent's tool list.
1. The parameters of the tool cannot be set manually.
2. There is an issue with the model used in the tool. The process of "model -> save -> apply to agent" is ineffective.
Contributor guide
Research direction
Reproduce the issue in the self-hosted Docker setup by adding tools to an Agent's tool list and following the model save/apply flow. Trace the Agent tool configuration and model-selection entry points; the fix is complete when tool parameters can be set manually and the selected model persists after saving and applying it to the Agent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100