Skip to content

Regression: task directory is not followed on terminal requestsΒ #7567

@pwilkin

Description

@pwilkin

App Version

3.26.3

API Provider

Google Gemini

Model Used

gemini-pro-2.5

Roo Code Task Links (Optional)

No response

πŸ” Steps to Reproduce

In a recent patch, the TerminalRegistry was patched to require a terminal that matches the task's directory. However, the registry does not track changes within the task, thus, the following sequence of actions will always fail:

execute_command cd subdir
execute_command command_from_subdir

πŸ’₯ Outcome Summary

The TerminalRegistry should track the changes in the Task's working directory based on the cwd of the last terminal that was used. Instead, it always assumes the root directory of the project, so the above sequence will always spawn a new terminal on the second execute_command call, reading to failure.

In a wider scope, this means that whenever any cd something && action commands are performed, a new terminal is spawned every time after this happens, since the only matching terminals are the ones that match the root directory of the project.

πŸ“„ Relevant Logs or Errors (Optional)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue - Needs ScopingValid, but needs effort estimate or design input before work can start.bugSomething isn't working

    Type

    No type

    Projects

    Status

    Issue [Needs Scoping]

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions