Remote Control: register a session without the 'session ready' push (fleet/automation use)

Feature request

Use case: we auto-spawn short-lived Claude Code sessions from cron (in tmux, claude --remote-control '<glance-name>' '<prompt>', completion detected via a Stop hook). The owner explicitly wants them all visible in the Remote Control session list so any of them can be inspected/steered on demand — his words: "I WANT TO BE ABLE TO INSPECT WHAT AUTO-SPAWNED CLAUDES ARE DOING, I just don't want my phone going nuts." A fleet of hourly agents means dozens of registrations a day, and every registration pushes a "session ready" notification to phone + desktop.

What we tried (v2.1.233):

• agentPushNotifEnabled: false and inputNeededNotifEnabled: false in the launch directory's project-scope .claude/settings.json — the session registered fine, and the ready push still fired (verified live with the notification recipient watching). So the registration/ready push appears to be server-side and outside the two documented toggles; the docs' "Beyond the two on/off toggles below, there is no per-event configuration" (remote-control.md) matches what we observed.
• (claude -p ... --remote-control X silently ignores the flag — print mode can't register at all — so headless mode is not a workaround for visibility.)

Ask (any one of these would do):

1. A launch flag like --remote-control-quiet / --remote-control-no-notify that registers the session in the list without the ready push;
2. A settings key honored at project scope (so a fleet launch directory can set it once);
3. Server-side: suppress or batch ready pushes for sessions matching --remote-control-session-name-prefix — that prefix already suggests fleet usage is an anticipated pattern.

Notifications for "needs input"/"Claude decides" are separately toggleable and that's fine — it's specifically the per-registration ready push that makes fleet visibility unusable.

Environment

• Claude Code 2.1.233, npm global, Debian 12 LXC (Proxmox), claude.ai Max plan login