claude remote-control asks about unattended use and rejects sandbox flags

What

claude remote-control lets you drive a Claude Code session on this machine from elsewhere. Its startup changed:

• Before starting, it now asks up front about serving this folder unattended, meaning tool calls may happen with nobody at the terminal. The question is skipped in single-session mode, and in worktree mode outside a git repository. If the question cannot be started, it reports an error and carries on. If you interrupt it, the program exits cleanly.
• The --sandbox and --no-sandbox flags, previously accepted and passed along, now cause an error: "is not supported by claude remote-control. The flag had no effect and was removed."
• The background (daemon) Remote Control worker now exits with an error if its configuration has a sandbox key: "The sandbox key is not supported for Remote Control. Remove it." It no longer passes a sandbox value on. Its handling of tengu_daemon_upgrade_defer_busy is unchanged.
• A startup debug line no longer logs sandbox=, and logs debugFile= only when one is set.

Why

Scripts or configurations that pass a sandbox option to Remote Control now fail at startup instead of being silently ignored, so remove the flag or key. Expect a new question the first time you start Remote Control in a folder.