[BUG] PowerShell Variable Corruption Bug - MAYBE_FIRST_START Injection

Environment

• Platform (select one):
• [ ] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [x] Other: Claude Code CLI
• Claude CLI version: 1.0.62
• Operating System: Windows
• Terminal: PowerShell

Bug Description

PowerShell commands executed through Claude Code are being corrupted with "MAYBE_FIRST_START" text insertion, causing command failures and timeouts.

```this happens in claude code:
Bash(powershell "Get-Process | Where-Object {$_.ProcessName -like 'CacheManager'} | Stop-Process -Force")
⎿ Error: Command timed out after 2m 0.0s MAYBE_FIRST_START.ProcessName : The term 'MAYBE_FIRST_START.ProcessName' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the
path is correct and try again.
At line:1 char:29

• Get-Process | Where-Object {MAYBE_FIRST_START.ProcessName -like '*Cac ...
• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
• CategoryInfo : ObjectNotFound: (MAYBE_FIRST_START.ProcessName:String) [], CommandNotFoundException
• FullyQualifiedErrorId : CommandNotFoundException

MAYBE_FIRST_START.ProcessName : The term 'MAYBE_FIRST_START.ProcessName' is not recognized as the name of a cmdlet,```

Steps to Reproduce

1. Execute a PowerShell command through Claude Code using Bash wrapper
2. Run: Bash(powershell "Get-Process | Where-Object {$_.ProcessName -like '*CacheManager*'} | Stop-Process -Force")
3. Observe the command execution failure

Expected Behavior

The PowerShell command should execute cleanly without any text corruption:

Get-Process | Where-Object {$_.ProcessName -like '*CacheManager*'} | Stop-Process -Force```