Roo Code

Ready VS Code family probe / automationProfile Windows Difficulty Easy

A Cline-lineage editor extension: it never picks a shell itself — commands run through the host editor's terminal or automation profile and inherit the family probe.

host editor settings.json · explicit automationProfile (the extension never picks a shell; it follows the host)

{
  "terminal.integrated.automationProfile.windows": {
    "path": "C:\\Users\\<你>\\AppData\\Local\\Programs\\Niubash\\niu.exe",
    "args": []
  }
}

Steps

Default: commands run through the host editor's terminal and the family-shared probe hits the installer-placed launcher — no configuration needed
For precise control: point automationProfile at niu.exe in the host editor (VS Code etc.) — the extension inherits it with the host

Verify

Run echo "SHELL=$SHELL"; uname -s in the host editor's integrated terminal — expect uname -s to start with MSYS_NT-

Rollback

Delete the terminal.integrated.automationProfile.windows setting

Notes & pitfalls

Roo Code descends from Cline and is likewise an editor extension: it never picks a shell itself — commands run through the host editor's terminal or automation profile and inherit the family probe

Sources

agents.md#vs-code（编辑器扩展节）
agents.md (the complete probe-mechanism document) ↗

Chinese edition of this page: /agents/roo-code/