Remote Control sessions from CLI don't associate with Desktop projects

Description

When using /remote-control (or /rc) from within a Claude Code CLI session to create a remote session, the session appears in Claude Code Desktop under "All projects" but is NOT associated with the specific project (e.g., buy.vodka-v3) even though the CLI session's cwd is within that project's folder.

Root Cause

Remote sessions created via CLI /remote-control have environment_id: "" (empty string) in their metadata. Desktop filters sessions by environment_id when a project is selected. Since the remote session has no environment_id, it doesn't match any project filter.

Steps to Reproduce

1. Open Claude Code Desktop with a project configured (e.g., "buy.vodka-v3" pointing to /Users/.../buy.vodka-v3)
2. Open Claude Code CLI in the same project directory
3. Run /remote-control or /rc in the CLI
4. Observe: the remote session appears at claude.ai/code/session_...
5. In Desktop, select the project from the dropdown
6. The remote session is NOT shown — it only appears under "All projects"

Expected Behavior

Remote sessions created via /remote-control from within a project directory should be associated with the corresponding Desktop project (matching by cwd to project folder, or by git remote).

Environment

• Claude Code CLI: 2.1.85 (Homebrew)
• Claude Code Desktop: 1.1.9134 (bundled CLI 2.1.78)
• macOS (darwin arm64)

Workaround

None currently. Users must use "All projects" view to see CLI-originated remote sessions.