Hi Onyeka,
Quick follow-up from our Windows/Codex testing pass on AgentRail.
While testing the current @agentrail-core/cli@0.1.6 package on Windows, we found that the local agent runner instructions still print POSIX shell commands like source ... && cd ..., which do not work directly in PowerShell.
We put together a small patch that keeps the existing macOS/Linux behavior, but prints PowerShell-compatible runner commands on Windows. It also adds Windows examples to the quick-start/SDK docs and fixes one Windows path issue in the docs contract test.
Focused verification passed locally:
node --test test/agent-management.test.ts test/docs-contract.test.js
npm run typecheck
npm run build
git diff --check
One extra note: when we manually expanded the service test globs on Windows, we found some broader Windows test-suite portability issues that look separate from this small runner-command patch. We kept notes on those privately so this first contribution can stay focused and easy to review.
Would you prefer that we open a small PR for the PowerShell runner command/docs fix, or send the patch file first for review?
Hi Onyeka,
Quick follow-up from our Windows/Codex testing pass on AgentRail.
While testing the current
@agentrail-core/cli@0.1.6package on Windows, we found that the local agent runner instructions still print POSIX shell commands likesource ... && cd ..., which do not work directly in PowerShell.We put together a small patch that keeps the existing macOS/Linux behavior, but prints PowerShell-compatible runner commands on Windows. It also adds Windows examples to the quick-start/SDK docs and fixes one Windows path issue in the docs contract test.
Focused verification passed locally:
One extra note: when we manually expanded the service test globs on Windows, we found some broader Windows test-suite portability issues that look separate from this small runner-command patch. We kept notes on those privately so this first contribution can stay focused and easy to review.
Would you prefer that we open a small PR for the PowerShell runner command/docs fix, or send the patch file first for review?