[BUG] Conda or venv Environment not synced across roles when starting as the orchestrator

[leehangyue]

Problem (one or two sentences)

Conda or venv Environment not synced across roles when starting as the orchestrator. The orchestrator seems not telling other roles it invokes like "ask" and "code" about the environment I specified in my prompt to the orchestrator.

Context (who is affected and when)

I tried to have roo edit an existing code repo and test on its own. I told the orchestrator to use a specific conda env with path pointing to the python executable. The orchestrator must know the right env to use, but the "ask" and "code" roles does not. They use plain "python" instead of i.e. /root/miniconda3/bin/python or C:/Users/my_user_name/AppData/Local/miniconda3/envs/my-env-name/python.exe

Reproduction steps

1. Windows10, intranet (no internet access), self-hosted GLM4.6, RooCode 3.35.2, VS Code 1.99.3 User setup.
2. Role: Orchestrator, Prompt: Add the feature "time" to the DataLoader in data_loader.py. Use this env for debug: C:/Users/my_user_name/AppData/Local/miniconda3/envs/my-env-name/python.exe. Test while you code.
3. Roo explored the code repo, then switched to "Ask", ran "dataset_inspector.py" to see data structure, in order to access the source of the "time" feature.
4. dataset_inspector.py failed importing some packages, because of the wrong environment.

Expected result

Roo (Ask) launch with: C:/Users/my_user_name/AppData/Local/miniconda3/envs/my-env-name/python.exe util/dataset_inspector.py /path/to/dataset/file

Actual result

Roo (Ask) launch with: cd util & python dataset_inspector.py /path/to/dataset/file

Variations tried (optional)

No response

App Version

3.35.2

API Provider (optional)

OpenAI Compatible

Model Used (optional)

GLM 4.6

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

The Orchestrator mode's customInstructions (in packages/types/src/mode.ts) instructs it to pass "all necessary context from the parent task" to subtasks. However, this guidance is too vague and doesn't explicitly mention environment-related settings like Python interpreter paths, virtual environments, or conda environments.

When a user specifies a Python environment path in their prompt to the Orchestrator, the LLM doesn't recognize this as critical context that must be forwarded to ALL subtasks. As a result, child tasks (like "ask" or "code" mode) default to using the system's python command instead of the user-specified path.

Proposed Solution

Update the Orchestrator mode's customInstructions to explicitly include environment/runtime settings as critical context that must always be forwarded to subtasks.

Changes:

1. Modify packages/types/src/mode.ts - Update the Orchestrator mode's customInstructions to add a new bullet point explicitly calling out environment settings:

*   Any environment or runtime settings specified by the user, including but not limited to:
    - Python interpreter paths (e.g., conda environments, virtualenvs)
    - Working directory requirements
    - Environment variables
    - Tool/CLI specific paths or configurations

This will be added to the list of things that "must include" in the instructions when delegating subtasks.

Benefits:

• Simple, low-risk change (only modifying prompt text)
• No changes to tool interfaces or task creation logic
• Guides the LLM to do the right thing naturally
• Applies to all types of environment settings, not just Python

Testing:

• Verify the mode configuration still validates correctly
• Test with a scenario similar to the reporter's use case (orchestrator delegating to ask/code mode with a specified Python path)

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[leehangyue]

@roomote I approve this plan, how to find packages/types/src/mode.ts?

[roomote]

Thanks for approving the plan! The file packages/types/src/mode.ts can be found in the repository at that exact path - it is in the packages/types/src directory.

You can view it on GitHub here: https://github.com/RooCodeInc/Roo-Code/blob/main/packages/types/src/mode.ts

I will now proceed with implementing the proposed changes and will open a PR shortly.

[roomote]

Opened a draft PR with my attempt at addressing this: #10682

The PR updates the Orchestrator mode's customInstructions to explicitly include environment/runtime settings as critical context that must always be forwarded to subtasks. Feedback welcome!