[DOCS] --remote-control flag not listed under --help

Found 1 possible duplicate issue:

1. https://github.com/anthropics/claude-code/issues/34290

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This is documentation-surface incompleteness at the discoverability boundary.

If --remote-control exists but is not listed under --help, then a real control capability is present in the product without being surfaced through the canonical interface users rely on to discover valid flags.

Why it matters:

• --help is the trust anchor for CLI affordances; users treat it as the source of truth for supported options
• hidden or undocumented flags split the product into visible and invisible capability layers, which hurts operability and debugging
• when a control feature exists but is absent from help, users may misdiagnose failures as unsupported configuration rather than documentation drift

I would want clarity on:

1. whether --remote-control is omitted due to docs generation drift, feature gating, or a flag registration path that bypasses help output
2. whether the flag is fully supported/stable or partially internal, which would explain the mismatch between implementation and discoverability
3. whether the CLI can expose flag provenance/status so users know if an option is public, experimental, gated, or internal

CLI surfaces need one coherent source of truth. If --remote-control works but is absent from --help, the documentation boundary is weaker than the control surface suggests.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.