[BUG] /feedback is categorically unavailable over Remote Control, including immediately after a session-ending error, with no alternative path named

Summary

/feedback is categorically unavailable over Remote Control (mobile), with no alternative reporting path surfaced — including immediately after a session-ending error, which is the single most natural moment a user would want to report one.

What was asked, precisely

A Remote Control (mobile) session ended mid-turn with a session-ending API error (see the related report at #83436 and the exact-match reports #82440 / #82139 for that error itself — this report is scoped only to the reporting-channel gap, not the crash). Immediately afterward, on the same screen, I typed /feedback to report what had just happened.

What was denied

/feedback isn't available over Remote Control.

That is the entire response. No alternative channel is named — no link, no "file it at X instead," no in-app fallback of any kind. The command is refused unconditionally for the whole surface, not scoped to the specific error or situation.

Why this matters beyond the single command

This turns any error that occurs on Remote Control into one that cannot be reported from where it happened. A user hits an opaque, unexplained failure on their phone, mid-task, and the one built-in path to report it responds by telling them that path doesn't exist there. In practice this means: remember the Request ID, switch to a different device or surface, and file separately — friction that most people encountering an error in the moment will not push through, so feedback about Remote-Control-specific problems is structurally underreported relative to desktop.

It's a compounding failure, not just an inconvenient one: the surface most likely to encounter certain classes of bugs (session interruptions, connectivity issues, mobile-specific rendering problems) is also the surface where in-context reporting is switched off.

Reproduction

1. Start a session with Remote Control (mobile client).
2. Trigger any error or otherwise want to leave feedback.
3. Type /feedback.
4. Observe the categorical refusal above, regardless of context.

What would resolve this

1. Enable /feedback over Remote Control, even in a reduced form (e.g., queue the report for delivery next time the desktop client is reachable, if the mobile bridge can't submit directly).
2. At minimum, have the refusal message name where feedback can be filed from that surface, instead of a dead end.

Environment

• Claude Code, Remote Control via mobile client (iOS)