[ralph-loop] CLAUDE_PLUGIN_ROOT not resolving on Windows - inline script fix

[yangzealliator-yz]

Problem

On Windows (with Git Bash), the ${CLAUDE_PLUGIN_ROOT} environment variable is not resolved, causing the ralph-loop plugin to fail:

/usr/bin/bash: line 31: /scripts/setup-ralph-loop.sh: No such file or directory

Environment

• OS: Windows 10/11
• Shell: Git Bash (via Claude Code)
• Plugin: ralph-loop

Root Cause

The ${CLAUDE_PLUGIN_ROOT} variable is not set/exported by Claude Code on Windows.

Proposed Solution

Replace external script call with inline bash script that doesn't depend on ${CLAUDE_PLUGIN_ROOT}.

Benefits:

1. Cross-platform (Windows, macOS, Linux)
2. No external dependencies
3. Self-contained
4. Also fixes ralph-loop fails with 'unbound variable' error - $ARGUMENTS not substituted in ```! block #167 ($ARGUMENTS works in inline scripts)

Related Issues

• [ralph-wiggum] Add Windows support - bash scripts fail on Windows/Git Bash #112 - Add Windows support
• ralph-loop fails with 'unbound variable' error - $ARGUMENTS not substituted in ```! block #167 - Variable substitution in code blocks
• ralph-wiggum 2 problems on Ubuntu on WSL #135 - Problems on WSL

Willing to Submit PR

I can submit a PR with the complete inline script fix.

[adilei]

We ran into the same issue with our plugin (microsoft/skills-for-copilot-studio). We found what seems to be a workaround, but would appreciate others verifying it:

While ${CLAUDE_PLUGIN_ROOT} template expansion appears broken on Windows, process.env.CLAUDE_PLUGIN_ROOT seems to be set correctly in hook subprocesses. So instead of relying on template substitution in the command string:

{
  "type": "command",
  "command": "bash \"${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh\""
}

We switched to node -e and read the env vars directly:

{
  "type": "command",
  "command": "node -e \"const r=process.env.CLAUDE_PLUGIN_ROOT; if(!r){process.exit(0)} require('child_process').execSync('bash '+r+'/scripts/setup.sh',{stdio:'inherit'})\""
}

This also sidesteps the diff/cp/mkdir portability issues since you can use Node's fs module instead of shell commands.

We've tested this on Windows (Claude Code v2.1.81) and it worked, but we haven't tested broadly. Would be great if others could confirm whether process.env.CLAUDE_PLUGIN_ROOT is reliably set on Windows. Our implementation: microsoft/skills-for-copilot-studio#81