Windsurf

Ready VS Code family probe / automationProfile Windows Difficulty Easy

A Code OSS lineage fork: the automation terminal inherits the family-shared probe — it hits the launcher once niubash is installed, no configuration needed.

settings.json · explicit automationProfile (the probe hits by default; this is for precise control)

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

Steps

Default: the family-shared probe hits the installer-placed launcher — no configuration needed
For precise control: point automationProfile at niu.exe in Windsurf's settings

Verify

echo "SHELL=$SHELL"; uname -s — expect uname -s to start with MSYS_NT-

Rollback

Delete the terminal.integrated.automationProfile.windows setting

Notes & pitfalls

Shares the same probe sequence as VS Code; not machine-tested — inferred from the shared lineage (the ZCode app.asar is the verified anchor)

Sources

agents.md#vs-code（VS Code 家族）
agents.md (the complete probe-mechanism document) ↗

Chinese edition of this page: /agents/windsurf/