ZCode

Ready VS Code family probe / automationProfile Windows Difficulty Easy

The family's only machine-verified member: the probe sequence in agents.md was read out of a ZCode app.asar (verified locally) — hits by default, no configuration.

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 ZCode'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

The verification anchor of the family probe: the hard-coded candidates and the PATH-relative arm were both read out of a ZCode app.asar (verified locally)
The other family members are inferred from the shared lineage — this entry is where the family's evidence chain starts

Sources

agents.md#vs-code（探针序列读自 ZCode app.asar）
agents.md (the complete probe-mechanism document) ↗

Chinese edition of this page: /agents/zcode/