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

Advanced Tool Intergration is different from version 0.15.3 #8598

New Issue
Closed
opened 2026-02-21 18:26:32 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:26:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @liangnet on GitHub (Feb 25, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

I pulled the latest version 0.15.3 and I found a difference point about path, they are
in document,
Image

in code,
Image

in version 0.15.0, I implemented a tool and located at core/tools/provider/builtin and run this tool successfully. However, after pulling the version 0.15.3, docker log showed many errors ad I saw the different directory structure. In order to find out what happened, I pull a clean one 0.15.3 and also see the Built-in tools such as

Image

So, I search the relevant words such as label and human_description, BUT! no one can be found.

Originally created by @liangnet on GitHub (Feb 25, 2025). ### 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 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. ### Provide a description of requested docs changes I pulled the latest version 0.15.3 and I found a difference point about path, they are in document, ![Image](https://github.com/user-attachments/assets/34012271-26e5-4e69-bb42-37c4847dd1be) in code, ![Image](https://github.com/user-attachments/assets/74fc5778-861c-425d-9792-8886adf5126a) in version 0.15.0, I implemented a tool and located at core/tools/provider/builtin and run this tool successfully. However, after pulling the version 0.15.3, docker log showed many errors ad I saw the different directory structure. In order to find out what happened, I pull a clean one 0.15.3 and also see the Built-in tools such as ![Image](https://github.com/user-attachments/assets/5042d9ee-bf01-4002-b702-c1ec03cc1baa) So, I search the relevant words such as label and human_description, BUT! no one can be found.
yindo added the 📚 documentationstale labels 2026-02-21 18:26:32 -05:00
yindo closed this issue 2026-02-21 18:26:32 -05:00
yindo commented 2026-02-21 18:26:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 25, 2025):

In version 0.15.3 of Dify, the directory structure for tool integration has changed. The YAML configuration files for tool integration are now located in the core/tools/provider/builtin directory. For example, if you are integrating a tool like GoogleSearch, you would create a google module (folder) under this directory and then create a google.yaml file within it. This YAML file should include the tool provider's basic information, such as the provider's name, icon, author, and other details necessary for frontend display [1].

Additionally, the built-in tools are organized under a "providers" directory, with each provider having its own subdirectory containing a "tools" directory. The tool configurations are stored as YAML files within these directories [2].

If you are encountering errors after updating to version 0.15.3, it might be due to these changes in the directory structure. You may need to adjust the location of your custom tool files to align with the new structure.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 25, 2025): <!-- Answer --> In version 0.15.3 of Dify, the directory structure for tool integration has changed. The YAML configuration files for tool integration are now located in the `core/tools/provider/builtin` directory. For example, if you are integrating a tool like GoogleSearch, you would create a `google` module (folder) under this directory and then create a `google.yaml` file within it. This YAML file should include the tool provider's basic information, such as the provider's name, icon, author, and other details necessary for frontend display <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/tools/quick-tool-integration.md)</sup>. Additionally, the built-in tools are organized under a "providers" directory, with each provider having its own subdirectory containing a "tools" directory. The tool configurations are stored as YAML files within these directories <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/tools/builtin_tool/provider.py)</sup>. If you are encountering errors after updating to version 0.15.3, it might be due to these changes in the directory structure. You may need to adjust the location of your custom tool files to align with the new structure. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5f7f76d8-a1ed-4ffd-86ea-5d6e79fe8be7?feedback_type=other)</sup>
yindo commented 2026-02-21 18:26:32 -05:00
Author
Owner
Copy Link
Copy Source

@liangnet commented on GitHub (Feb 28, 2025):

The Advanced Tool Integration has moved to Dify-Official-Plugin, But the document not yet

https://github.com/langgenius/dify-official-plugins/tree/main/tools

@liangnet commented on GitHub (Feb 28, 2025): The Advanced Tool Integration has moved to Dify-Official-Plugin, But the document not yet https://github.com/langgenius/dify-official-plugins/tree/main/tools
yindo commented 2026-02-21 18:26:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 31, 2025):

Hi, @liangnet. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • Discrepancy in directory structure between versions 0.15.0 and 0.15.3.
  • Errors in locating elements like "label" and "human_description."
  • Directory structure changes acknowledged; YAML files now in core/tools/provider/builtin.
  • Advanced Tool Integration moved to Dify-Official-Plugin; documentation update needed.

Next Steps

  • Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open.
  • If no further activity occurs, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 31, 2025): Hi, @liangnet. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Discrepancy in directory structure between versions 0.15.0 and 0.15.3. - Errors in locating elements like "label" and "human_description." - Directory structure changes acknowledged; YAML files now in `core/tools/provider/builtin`. - Advanced Tool Integration moved to Dify-Official-Plugin; documentation update needed. **Next Steps** - Is this issue still relevant to the latest version of the Dify repository? If so, please comment to keep the discussion open. - If no further activity occurs, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 stale 📚 documentation
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#8598
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?