claude remote-control should support the same configuration flags as interactive mode (--plugin-dir, system prompt)

Summary

claude remote-control (server mode) spawns up to 32 independent sessions, but those sessions don't inherit the same configuration as a regular claude interactive session. Specifically, there's no way to pass --plugin-dir or configure the system prompt for spawned sessions.

This means users who depend on plugins (e.g., MCP servers loaded via --plugin-dir) or a custom system prompt can't use server mode's multi-session capability with their full environment.

Expected behavior

claude remote-control should accept the same command-line flags as claude interactive mode, so that each spawned session starts with the correct plugin directory and system prompt. For example:

claude remote-control --plugin-dir /path/to/plugins --system-prompt "..."

Current workaround

Start claude with the desired flags and then run /remote-control from within the interactive session:

claude --plugin-dir /path/to/plugins
# then inside the session:
/remote-control

This works but limits you to a single shared session — phone and Mac share the same conversation context, losing the multi-session (up to 32) capability that server mode provides.

Environment

• Claude Code v2.1.76
• macOS (Darwin 25.2.0)