[BUG] Custom project slash commands missing from / picker on Remote Control; /feedback unavailable on Remote Control and VSCode extension

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Custom project slash commands (defined in .claude/commands/*.md) don't appear in the / picker when using Claude Code Remote Control (mobile app / claude.ai web), even for commands that existed well before the remote session started — so it isn't a stale-scan/caching issue. Separately, /feedback itself appears unavailable in more environments than just the CLI:

Custom slash commands missing from picker over Remote Control — project-level commands under .claude/commands/ (e.g. om-ingest, om-watch) don't show in the / autocomplete picker on Remote Control (mobile app / claude.ai web), even though they're pre-existing and work fine from a local terminal CLI session. Not confirmed whether they still execute if typed out in full — only that they don't appear in the picker.
/feedback unavailable over Remote Control — tried running /feedback from Remote Control to report finding #1 in the moment; command wasn't available there at all.
/feedback also unavailable in the VSCode extension environment — separately tried /feedback from the Claude Code VSCode extension (not Remote Control) and got "/feedback isn't available in this environment." So the gap isn't Remote Control-specific — at minimum two non-CLI environments lack it. Only confirmed working from a plain terminal CLI session so far.

What Should Happen?

Custom project slash commands should appear in the picker consistently across CLI, Remote Control, and the VSCode extension.
/feedback should be available (or an equivalent reporting path clearly surfaced) in every environment Claude Code runs in — otherwise there's no way to report an environment-specific bug from within that same environment.

Error Messages/Logs

Steps to Reproduce

Finding 1 — custom commands missing from Remote Control picker:

On a desktop/CLI session in a project with custom commands under .claude/commands/*.md, confirm the commands work locally (e.g. type /om-ingest and it autocompletes/runs).
Start a Remote Control session on the same project from the mobile app or claude.ai web.
Type / in the Remote Control chat input.
Observe: the custom project commands don't appear in the picker, even though they predate this session and work fine locally.
Finding 2 — /feedback unavailable over Remote Control:

While in a Remote Control session (mobile app or claude.ai web), type /feedback.
Observe: command is not available/not recognized in this environment.
Finding 3 — /feedback unavailable in VSCode extension:

Open a project in the Claude Code VSCode extension.
Type /feedback.
Observe: response is "/feedback isn't available in this environment."
For contrast, run /feedback from a plain local terminal CLI session in the same project — it works there.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.205

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_