[BUG] Agent Teams on windows with psmux launching with unix style path not windows powershell style.

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When claude trys to run up a team mate on windows, it is using the wrong path for claude binary (quoted) in powershell.

Work-around:
Remove the cd && at the front of the command and change the quoted claude path to just claude and re-run the command the team member starts up as expected.

env CLAUDECODE=1 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude --agent-id Cara@dev-test-team --agent-name Cara --team-name dev-test-team --agent-color yellow --parent-session-id REDACTED

What Should Happen?

Claude code should run the team mate as expected not get an error trying to run claude.

Error Messages/Logs

cd 'I:\dev-disk-saver-app' && env CLAUDECODE=1 CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 'C:\Users\Liam\.local\bin\claude.exe' --agent-id Cara@dev-test-team --agent-name Cara --team-name dev-test-team --agent-color yellow --parent-session-id REDACTED


> The filename, directory name, or volume label syntax is incorrect.


From what I can tell it is caused by this
`'C:\Users\Liam\.local\bin\claude.exe'` which should just be `claude` or perhaps unquoted on windows `C:\Users\Liam\.local\bin\claude.exe`

Steps to Reproduce

1. Enable claude code experiemental teams in claude code settings env I also set teammateMode to auto

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  },
  "teammateMode": "auto"
}

1. Install psmux for tmux on windows, may happen without this given its the command at fault?

https://github.com/psmux/psmux

winget install psmux

3.
Install env shim

winget install uutils.coreutils

Made a .tmux.conf in my user profile (likely irrelevant)

# psmux - Bring the power of tmux to windows https://github.com/psmux/psmux

# Mouse support
set -g mouse on

# Passthrough (for image rendering, OSC sequences, etc.)
set -g allow-passthrough on

# Better colors
set -g default-terminal "tmux-256color"
set -ag terminal-overrides ",xterm-256color:RGB"

# No delay on escape (important for vim/neovim)
set -sg escape-time 0

# Longer scrollback
set -g history-limit 50000

# Start windows and panes at 1, not 0
set -g base-index 1
setw -g pane-base-index 1
set -g renumber-windows on

# ── Prefix ────────────────────────────────────────────────────────
# Change prefix from C-b to C-a (easier to reach)
unbind C-b
set -g prefix C-a
bind C-a send-prefix

# ── Splits ────────────────────────────────────────────────────────
# Intuitive split bindings, open in current path
bind | split-window -h -c "#{pane_current_path}"
bind - split-window -v -c "#{pane_current_path}"
bind c new-window -c "#{pane_current_path}"

# ── Resize panes with arrow keys ──────────────────────────────────
bind -r Up    resize-pane -U 5
bind -r Down  resize-pane -D 5
bind -r Left  resize-pane -L 5
bind -r Right resize-pane -R 5

# ── Status bar ────────────────────────────────────────────────────
set -g status-interval 5
set -g status-left-length 40
set -g status-right-length 60

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v2.1.90

Platform

Other

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

It would be a powershell terminal inside vscode.