Packaged agent commands fail in Windows PowerShell because Unix env syntax is mandatory

[PionneerZ]

The packaged Codex, Claude Code, Cursor, OpenClaw, and skills.sh instructions require every CLI invocation to start with Unix env NAME=value ... syntax. Stock Windows PowerShell has no env executable, so the command fails before Node, calle, or npx starts.

Tested at commit e497e1a01e171f9559f87e0f998318a9efc06609 on Windows PowerShell 7 with Node.js v24.12.0.

Reproduction

Run the first documented Codex command literally:

Get-Command env -ErrorAction SilentlyContinue
env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.11 node packages/cli/bin/calle.js --version

Actual result:

Get-Command env: NOT FOUND
env: The term 'env' is not recognized as a name of a cmdlet, function,
script file, or executable program.

Changing the tail to either calle --help or npx -y @call-e/cli --help gives the same pre-execution failure because every fallback retains the shared env prefix.

Control experiment using native PowerShell syntax:

$env:CALLE_SOURCE = 'codex'
$env:CALLE_INTEGRATION = 'codex_plugin'
$env:CALLE_INTEGRATION_VERSION = '0.1.11'
node packages/cli/bin/calle.js --version

Actual: 0.5.0, exit code 0.

Scope

At this commit there are 145 command lines beginning with env CALLE_SOURCE under packages/, skills/, and docs/. The incompatible mandatory pattern appears in:

• packages/codex-plugin/plugin/skills/calle/SKILL.md:56-80
• packages/codex-plugin/plugin/skills/calle/references/commands.md
• packages/claude-plugin/plugin/skills/calle/SKILL.md
• packages/cursor-plugin/plugin/skills/calle/SKILL.md
• packages/openclaw-cli-skill/skills/phone-call-calle/SKILL.md
• skills/calle/SKILL.md
• docs/install/CALL-E-installation-guide.md

This blocks --help, auth, MCP readiness, planning, execution, and status on a normal Windows PowerShell host. The agent instructions also declare the attribution prefix mandatory, so a conforming agent cannot safely omit it.

Suggested fix

Prefer a cross-platform launcher or internal CLI attribution flags so the command itself is shell-independent. As a minimal documentation fix, add explicit Bash, PowerShell, and cmd.exe forms and instruct integrations to select based on the current shell. Add a Windows CI check that launches at least one literal generated readiness command under pwsh.

All repository tests and pnpm check pass, showing the current validation gap. Targeted searches of the current public issues for PowerShell and env CALLE_SOURCE found no duplicate.

This report and reproduction were prepared with AI coding assistance.