Kiro

Ready VS Code family probe / automationProfile Windows Difficulty Easy

AWS's agentic IDE (Code OSS lineage): wired per the family-shared probe on an inferred basis — agents.md marks it inferred, not machine-tested; it should hit the launcher once niubash is installed.

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 should hit the installer-placed launcher (inferred, not machine-tested)
For precise control: point automationProfile at niu.exe in Kiro'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 one member the original probe list did not name: grouped into the family on Code OSS lineage (agents.md marks it inferred) — per-machine confirmation is welcome
Shares the same probe sequence as VS Code; verify with the family-wide command

Sources

agents.md#vs-code（Kiro 为 inferred 成员）
agents.md (the complete probe-mechanism document) ↗

Chinese edition of this page: /agents/kiro/