/design unavailable over Remote Control: no design skill, /design consent returns 403

Summary

/design does not work in a Claude Code session driven through Remote Control. The same command works when run directly on my machine. In the remote session:

• The agent can't see a design skill, so asking it to "/design 5 solutions" gets the answer that no such skill exists.
• Typing /design shows only a stub: "run /design consent or /design revoke".
• /design consent fails with 403.

Expected: /design behaves the same over Remote Control as it does locally. If a login is missing, the session should point to a way to fix it that works remotely, not dead-end.

Steps to reproduce

1. On a machine where /design works in a local Claude Code session, start a session and connect to it through Remote Control (from phone or web).
2. Ask: /design create 5 possible solutions for <feature>, all in one artifact.

• The agent reports there is no design skill. The skill list it receives has no design entry, and none exists under ~/.claude/skills or in the plugin cache.

1. Run /design with or without arguments.

• The only output is: "In this session /design only manages agent access to Claude Design projects: run /design consent or /design revoke."

1. Run /design consent.

• Output: Couldn't record Design agent access for your Claude Design projects — Request failed with status code 403. Try again, or run /design-login to authorize Claude Design for this account.

Actual vs expected

| | Local session | Remote Control session |
|---|---|---|
| /design <prompt> | Creates a design artifact | Stub message only; agent has no design capability |
| /design consent | n/a (works) | 403 |
| File delivery fallback (SendUserFile) | n/a | not delivered: this session is not on a project thread |

So the remote session has no working way to produce a design artifact at all: no design skill, consent fails, and file delivery fails too.

Environment

• Claude Code 2.1.283
• Linux (Ubuntu, kernel 6.8), session controlled via Remote Control
• Same account that uses /design successfully locally

Related

• #90686: same /design-consent 403 dead-end, reported in the VS Code extension. This looks like the same missing user:design authorization, now also hitting Remote Control sessions.