Qwen3 via Ollama reports no access to Developer Extension
Describe the bug
LLM states:
I currently don't have direct access to code files or developer tools in this environment. The available tools are limited to:
- Task management (
todo)- Memory storage/retrieval (
memory)- Extension management (
extensionmanager)
But it's definitely enabled under goose configure:
◆ enable extensions: (use "space" to toggle and "enter" to submit) │ ◼ Extension Manager (<) │ ◼ developer │ ◼ memory │ ◼ todo
To Reproduce Steps to reproduce the behavior:
- Start Goose with Ollama Qwen3
- Ask it to edit a file
- It will not edit, and usually will state why (missing extension)
Expected behavior Qwen3 finds the tool, or if it's truly not accessible for Qwen3 it warns about that like with other models.
Please provide following information:
- OS & Arch: Windows 11 23H2 (no WSL)
- Interface: CLI
- Version: 1.12.1
- Extensions enabled: Extension manager, developer, memory, todo
- Provider & Model: Qwen3-14b
Additional context None
~~I found another comment mentioned permissions.yaml and it seems like it might be working after I changed it to match the settings below:~~
user:
always_allow:
- todo__todo_read
ask_before:
- memory__remember_memory
- platform__search_available_extensions
- developer__shell
- developer__text_editor
never_allow: []
~~But this still seems like a bug that I could end up in this state with no notice or warning.~~
Edit: Well, it used text editor, but it didn't make any of the changes it claims to have made on the disk.
Qwen3-14b is just not going to cut for general tool use. if you switch off all the tools and keep only the developer tools, maybe. but for me even asking it to list the files in the current folder is going to get it confused.
I put this up with more diagnostics and it has a test script. take it for a spin, but closing this for now:
https://github.com/block/goose/pull/5609
Thanks for your reply @DOsinga. I couldn't get any model in Ollama to use tools. Is there any you know should work to validate that tools are usable?
you can't? it uses tools for me, just not very well; what happens if you run that script?