1.8

[benrey]

when tools are used the path is entered twice

When goose tries to edit files or use commands from tools dev tools I'm guessing and strreplace is the command but probably happens to others it sends the command and it attaches the location twice so it knows its in the root of the project but when it sends the location relative to the root of the project the tool adds it twice:
/users/username/project/app/components/app/components/filename.ext and errors out.

To Reproduce
Steps to reproduce the behavior:

1. Use a model that allows tooling
2. Ask the chat to fix a simple problem.
3. It will continue to send the same command over and over and is not intuitive enough to try different commands or try another approach.
4. See error
   The persistent error indicates an incorrect file path being referenced. The correct absolute path should be /Users/username/git/appname/app/components/filename.ext (without the duplicate /app/components). Let's attempt one final correction with the proper path:

Expected behavior
Tooling just works and edits files etc.

Please provide following information:

• OS & Arch: MAC OSX m4 max pro
• Interface: Desktop
• Version: v1.8.0
• Extensions enabled: memory, developer tools
• Provider & Model: qwen-coder53b

Additional context
Also tried computer controller without developer tools turned on and it fails asa well

[alexhancock]

This seems like a model specific issue from my testing just now

I don't repro the same issue with either Claude Sonnet 4 for example, or qwen2.5-coder

Which provider are you using, and which exact model are you using? I'm not familiar with a 53b qwen-coder

[DOsinga]

Possibly related: #4634

[alexhancock]

I've merged #4641 which we expect may make this better. @benrey let me know when you can get back to me with details of what model exactly you were seeing this with.

[benrey]

Sorry for the late response. yeah it's just qwen3 coder. I just uninstalled and went back to 1.7 and everything started working again. So yeah I think there is something wrong with tools and I'll try that branch to see if it fixes the issue and report back.

[DOsinga]

closing this for now, assuming the fix @alexhancock mentioned works