Models need clear workspace command execution guidelines

[KJ7LNW]

When working with the monorepo structure, AI models often fail to properly specify the working directory when executing commands in specific workspaces.

Problem

• Models frequently run commands from the root directory without specifying the correct workspace
• This leads to incorrect package installations, test failures, and build errors
• Commands executed in the wrong context can affect unintended parts of the codebase

Solution Needed

• Clear documentation on how to execute commands in specific workspaces
• Explicit instructions to always use the <cwd>workspace/directory</cwd> parameter
• Examples of correct command execution in different workspace contexts

This issue is related to the broader monorepo understanding problem (#4295) but specifically focuses on command execution context.

[dosubot]

To ensure commands are executed in the correct workspace within a monorepo, always specify the working directory using the <cwd>workspace/directory</cwd> parameter. This prevents issues like incorrect package installations, test failures, and build errors that occur when commands run from the root directory.

For example, to run a command in a specific workspace, use:

<execute_command>
  <command>git status</command>
  <cwd>./my-project</cwd>
</execute_command>

This pattern applies to any command that should be scoped to a particular workspace or package directory. The <cwd> parameter sets the working directory for the command, ensuring it runs in the intended context. If omitted, the command defaults to the root or the first workspace folder, which can lead to unintended side effects in a monorepo setup. More details and examples are available in the Roo Code documentation for executing commands in a specific directory.

The same principle applies to server processes and other tools: always set the cwd parameter to the relevant workspace directory to avoid context-related errors. For further reference, see the documentation on using the cwd parameter.

While Roo Code has migrated to a monorepo structure and improved its build and dependency management workflows, there is currently no dedicated documentation section or discussion thread specifically addressing command execution context in monorepos or issue #4295. If you need more detailed or scenario-specific examples, expanding the documentation with additional workspace-specific command patterns would be beneficial.

To reply, just mention my name @dosu.

---

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

[hannesrudolph]

stale