langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

searxng with agent #926

New Issue
Closed
opened 2026-02-16 10:21:01 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 10:21:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @nicho2 on GitHub (Jan 9, 2026).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues Dify issues & Dify Official Plugins, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.1

Plugin version

0.0.7

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I don't understand what is the problem !!

Image

✔️ Error log

Image
Originally created by @nicho2 on GitHub (Jan 9, 2026). ### Self Checks - [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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.1 ### Plugin version 0.0.7 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I don't understand what is the problem !! <img width="467" height="577" alt="Image" src="https://github.com/user-attachments/assets/d57fcf09-a6c6-4350-a8eb-c6ee8c8735cf" /> ### ✔️ Error log <img width="668" height="130" alt="Image" src="https://github.com/user-attachments/assets/746b1155-dd74-468d-9458-d03442b58434" />
yindo added the bug label 2026-02-16 10:21:01 -05:00
yindo closed this issue 2026-02-16 10:21:01 -05:00
yindo commented 2026-02-16 10:21:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 9, 2026):

The error "tool parameter query not found in tool config" means the searxng_search tool is missing a required parameter called query in its configuration. This parameter is essential—it represents the search string that SearXNG uses to perform a search. If it's not provided, the tool cannot work and will fail with this error.

To fix this, make sure that when you configure or invoke the searxng_search tool (whether in the agent setup or in your workflow), you supply a value for the query parameter. The configuration for this tool explicitly marks query as required and expects it to be a string—usually the keywords or phrase you want to search for. If the UI does not expose a field for this, check your agent or tool setup and ensure the query parameter is included in the tool's parameters section, or update your workflow to pass it correctly. For reference, see the tool config definition and implementation:

If you need to pass dynamic queries (for example, from user input or LLM output), ensure your agent or workflow is set up to provide this value at runtime. If you have further trouble, let me know how you're configuring the agent and I can help you pinpoint where to add the query parameter.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 9, 2026): <!-- Answer --> The error "tool parameter query not found in tool config" means the searxng_search tool is missing a required parameter called `query` in its configuration. This parameter is essential—it represents the search string that SearXNG uses to perform a search. If it's not provided, the tool cannot work and will fail with this error. To fix this, make sure that when you configure or invoke the searxng_search tool (whether in the agent setup or in your workflow), you supply a value for the `query` parameter. The configuration for this tool explicitly marks `query` as required and expects it to be a string—usually the keywords or phrase you want to search for. If the UI does not expose a field for this, check your agent or tool setup and ensure the `query` parameter is included in the tool's parameters section, or update your workflow to pass it correctly. For reference, see the tool config definition and implementation: - [`searxng_search.yaml`](https://github.com/langgenius/dify-official-plugins/blob/f10c92c01654946287a99085d73d5c488df904a2/tools/searxng/tools/searxng_search.yaml#L17-L107) - [`searxng_search.py`](https://github.com/langgenius/dify-official-plugins/blob/f10c92c01654946287a99085d73d5c488df904a2/tools/searxng/tools/searxng_search.py#L7-L41) If you need to pass dynamic queries (for example, from user input or LLM output), ensure your agent or workflow is set up to provide this value at runtime. If you have further trouble, let me know how you're configuring the agent and I can help you pinpoint where to add the `query` parameter. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9dbf7382-751c-4d41-b9e8-d1fed4a031d2?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20error%20%22tool%20parameter%20query%20not%20found%20in%20tool%20config%22%20means%20the%20searxng_search%20tool%20is%20missing%20a%20required%20parameter%20called%20%60query%60%20in%20its%20configuration.%20This%20parameter%20is%20essential%E2%80%94it%20represents%20the%20search%20string%20that%20SearXNG%20uses%20to%20perform%20a%20search.%20If%20it%27s%20not%20provided%2C%20the%20tool%20cannot%20work%20and%20will%20fail%20with%20this%20error.%0A%0ATo%20fix%20this%2C%20make%20sure%20that%20when%20you%20configure%20or%20invoke%20the%20searxng_search%20tool%20%28whether%20in%20the%20agent%20setup%20or%20in%20your%20workflow%29%2C%20you%20supply%20a%20value%20for%20the%20%60query%60%20parameter.%20The%20configuration%20for%20this%20tool%20explicitly%20marks%20%60query%60%20as%20required%20and%20expects%20it%20to%20be%20a%20string%E2%80%94usually%20the%20keywords%20or%20phrase%20you%20want%20to%20search%20for.%20If%20the%20UI%20does%20not%20expose%20a%20field%20for%20this%2C%20check%20your%20agent%20or%20tool%20setup%20and%20ensure%20the%20%60query%60%20parameter%20is%20included%20in%20the%20tool%27s%20parameters%20section%2C%20or%20update%20your%20workflow%20to%20pass%20it%20correctly.%20For%20reference%2C%20see%20the%20tool%20config%20definition%20and%20implementation%3A%20%20%0A-%20%5B%60searxng_search.yaml%60%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/f10c92c01654946287a99085d73d5c488df904a2/tools/searxng/tools/searxng_search.yaml%23L17-L107%29%20%20%0A-%20%5B%60searxng_search.py%60%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/f10c92c01654946287a99085d73d5c488df904a2/tools/searxng/tools/searxng_search.py%23L7-L41%29%0A%0AIf%20you%20need%20to%20pass%20dynamic%20queries%20%28for%20example%2C%20from%20user%20input%20or%20LLM%20output%29%2C%20ensure%20your%20agent%20or%20workflow%20is%20set%20up%20to%20provide%20this%20value%20at%20runtime.%20If%20you%20have%20further%20trouble%2C%20let%20me%20know%20how%20you%27re%20configuring%20the%20agent%20and%20I%20can%20help%20you%20pinpoint%20where%20to%20add%20the%20%60query%60%20parameter.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2400)
yindo commented 2026-02-16 10:21:02 -05:00
Author
Owner
Copy Link
Copy Source

@nicho2 commented on GitHub (Jan 16, 2026):

OK , I upgraded to Dify version 1.11.4, deleted the Node agent, rebuilt it, and now it's OK.

@nicho2 commented on GitHub (Jan 16, 2026): OK , I upgraded to Dify version 1.11.4, deleted the Node agent, rebuilt it, and now it's OK.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
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-official-plugins#926
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?