crow-workspace/batch skills ignore remote control setting when launching sessions

[dhilgaertner]

Problem

When remote control is enabled in Crow's app settings (remoteControlEnabled: true), new sessions created from the Manager tab via the /crow-workspace or /crow-batch-workspace skills come up with remote control off. The global preference is not applied to auto-launched Claude Code instances in these sessions.

Expected

If remote control is enabled globally, any session auto-launched via these skills should start Claude with remote control on — the same way it behaves for sessions started through the app UI.

Root Cause

setup.sh (used by both skills) launches Claude via crow send with a hardcoded command that does not include --rc:

Projects/.claude/skills/crow-workspace/setup.sh:476
local send_text="cd $WORKTREE_PATH && $claude_bin --permission-mode plan \"\$(cat $prompt_path)\"\\n"

There is no branch that inspects the global remoteControlEnabled config (or the equivalent logic in ClaudeLaunchArgs.argsSuffix) before composing the command, so skill-launched sessions never receive --rc even when the app has it enabled.

The same gap likely exists in crow-batch-workspace/setup.sh since it shares the launch pattern.

Proposed Fix

Before composing send_text, have setup.sh check the global remote-control preference (e.g. via a new crow get-config query, or by reading ~/.local/share/crow/config.json / .claude/config.json) and append the same --rc --name '<session-name>' suffix that ClaudeLaunchArgs.argsSuffix produces for app-initiated sessions. This keeps skill-launched and app-launched sessions consistent.

Files Affected

• Projects/.claude/skills/crow-workspace/setup.sh
• Projects/.claude/skills/crow-batch-workspace/setup.sh (same launch pattern)