Repository navigation
Run the Windows-Native Check for the Case-Sensitive Agents Keyword From #3130 #3138
Description
Context
#3130 made the Windows loaders match the all keyword and tool names case-sensitively, as Linux does, and was verified under Linux pwsh and the CI Windows unit test job only. This issue is the Windows-native check that pull request left owed. It needs a Windows host, so it belongs to the windows lane.
The uppercase half has already been run by hand on Windows and passed: -Agents ALL refused with Unknown tool "ALL", -List names the managed tools. The lowercase half has not run, because a second run in the same pwsh session hit #3137, the bootstrap lock outliving a run in an interactive session.
The Check
From a hub checkout on develop (or on main once #3130 is promoted, dropping -Ref develop), each command in its own process so #3137 does not interfere:
git switch develop
git pull --ff-only
pwsh -NoProfile -File ./host-setup/bootstrap.ps1 -Agents all -Ref develop -DryRun # expect: -Install -All, every managed tool listed, exit 0
pwsh -NoProfile -File ./host-setup/bootstrap.ps1 -Agents ALL -Ref develop -DryRun # expect: Unknown tool "ALL", exit 1
pwsh -NoProfile -File ./host-setup/bootstrap.ps1 -Agents Herdr -Ref develop -DryRun # expect: Unknown tool "Herdr", exit 1
pwsh -NoProfile -File ./host-setup/bootstrap.ps1 -Agents herdr -Ref develop -DryRun # expect: herdr's install step printed, exit 0Repeat the four under Windows PowerShell 5.1 (powershell -NoProfile -ExecutionPolicy Bypass -File ...), since -ccontains and -ceq are the operators that changed and 5.1 is the other host the loader supports.
Done
All eight runs match their expectation, with the output recorded in a comment here. A mismatch is a defect in #3130's change and gets its own issue. This one closes once the comment is posted.
Activity
ptr727 commentedon Oct 16, 2026
Windows-Native Check Results
Run on a Windows 11 host against
developat 722a458 (the #3130 merge), with pwsh 7.6 and Windows PowerShell 5.1, each command in its own process,-Ref develop -DryRunon every run.-AgentsallSelected: claude codex opencode herdr cswapALLUnknown tool "ALL", -List names the managed toolsHerdrUnknown tool "Herdr", -List names the managed toolsherdrSelected: herdrallSelected: claude codex opencode herdr cswapALLUnknown tool "ALL", -List names the managed toolsHerdrUnknown tool "Herdr", -List names the managed toolsherdrSelected: herdrThe case-sensitive matching #3130 introduced behaves as intended under both hosts: lowercase
allexpands to every managed tool, lowercaseherdrselects that tool, and the capitalized forms are refused by name.The
allExit Code Is Not a #3130 DefectBoth
allruns exit 1 rather than the 0 this issue expected, and the cause is codex rather than the keyword. On this host codex is not installed, andinstall-agents.ps1's codexInstallblock deliberately warns that codex documents no Windows installer outside a package manager and returns 1, so the run reportsFailed: codexeven under-DryRun. Every other selected tool reported its expected dry-run line. Any Windows host without codex sees the same exit 1 from-Agents all, so the expectation here, not #3130's change, was off, and no defect issue is filed for it.The Default Directory Was Held During the Check
The first attempt, against the default bootstrap directory, was refused the lock on every run: a process outside this check still held it, consistent with #3137, where a run typed at an interactive prompt keeps the lock for the life of that session. The eight runs above therefore used
-Dirpointing at a fresh scratch directory, which leaves the keyword behavior under test unchanged. #3137's fix is in flight separately.