Context should have current terminal path

[andymartin]

RooCode is always changing directories to run code, etc. but never knows where it is so it wastes a lot of tokens getting commands correct.

[cte]

I think @KJ7LNW has done some work in this area, which seems to have improved it (at least for me).

[KJ7LNW]

RooCode is always changing directories to run code, etc. but never knows where it is so it wastes a lot of tokens getting commands correct.

Paste the API details by clicking here when that happens:

[KJ7LNW]

also, what version of Roo?

[agentience]

Has there been any further movement on this? It happens quite often for me. Just noticed a case where it cost me $.55 for Roo to figure out it was in the wrong directory. Yikes!

Roo: 3.18.1
MacOS: Sequoia 15.5 (24F74)
VS Code: 1.100.2
Shell: zsh (not using oh-my-zsh)

The command was chmod +x

IMHO this might just need to good old brute forcing until a more elegant solution can be found - like double checking any file operations against the cwd in the console, just before the are run. Or just making them all absolute paths. The latter would add more token usage, but not compared to the corrections.

[KJ7LNW]

https://docs.roocode.com/advanced-usage/available-tools/execute-command

You can tell the model to use cwd for every command invocation and it should fix that, at least depending on how smart the model is.

I have not had any problems with sonnet-3.[57] or gemini-2.5 ever since implementing cwd handling, for me has always figured it out in the very next request.

[agentience]

Thanks. I'm using Claude 3.7 Sonnet. Can you provide a little more guidance on how to tell the model? I've put the following in the mode's custom instructions, but not seeing any change:
'ALWAYS USE THE cwd OPTION WHEN USING THE execute_command TOOL'

[KJ7LNW]

actually I do not have any special instructions, figures it out because cwd is provided with all command execution output and the model usually says something like "I see I was already in that directory let me try again" and then it always works on the second try. Example:

[execute_command for 'gh pr list --repo RooVetGit/Roo-Cline --limit 10'] Result:
Command executed in terminal  within working directory '/home/ewheeler/src/roo/Roo6'. Exit code: 0
Output:

Showing 10 of 163 open pull requests in RooVetGit/Roo-Cline

However if you do want to force cwd, Sonnet responds very well to MUST...because in instructions (ask you which words it believes in part the most critically and it will mention "must" as being pretty high):

You MUST ALWAYS use path when using the <execute_command> tool because then the correct term the will be used'