Replies: 2 comments 2 replies
|
If you disable them on the project level, they will still form part of the mcp tools but just be disabled internally. Instead you should create a custom context and disable the tools there, then Qwen won't think that they exist and won't try calling them |
2 replies
|
Btw, if you have good results with the custom context, you could consider making a PR with qwen-coder context so that we can recommend it to other users for qwen |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm playing with (Unsloth) Qwen3-Coder-30B-A3B-Instruct and Serena, and Qwen gets hung up in think_about_collected_information - think_about_task_adherence - think_about_collected_information - ... loops very quickly. For testing, I tried disabling those tools in
.serena/project.yml, but they get called quite frequently anyways, erroring out, then getting retried. Not sure where to go from here. Is there a way to hide tools completely, or would it be an option to make disabled tools return something neutral rather than an error?All reactions