[BUG] Remote Control (Android app): /clear leaves the session stuck on a loading spinner and silently drops the next prompt

What's Wrong?

When I send /clear from the Android Claude app while connected to a Remote Control session, the session gets stuck and I lose whatever I type next.

What I see, in order:

1. /clear shows up twice in the conversation.
2. Then a line that says (no content).
3. Then the loading/progress animation starts and never stops.

While it sits in that stuck loading state, anything I type next is shown in light gray and is never picked up. The session never processes it. The only way out is to close the window and reopen it. After reopening, the loading animation is gone and I can type again, but the prompt I had entered is lost.

I have lost long prompts this way several times, because the input looks like it was accepted but is silently dropped.

What Should Happen?

/clear should reset the context and leave the session ready for input. It should show once, finish cleanly, and the next message I type should be sent and processed normally. Nothing should be left spinning, and no typed input should be silently dropped.

Steps to Reproduce

1. Start a Claude Code session on a host (mine runs on WSL2) and enable Remote Control.
2. Connect to that session from the Android Claude app.
3. Send /clear as its own message from the app.
4. Watch /clear appear twice, then (no content), then the loading animation start and stay running.
5. Type a new message. It appears in light gray and is never sent or answered.
6. Close the window and reopen it. The loading animation is gone and input works again, but the message from step 5 is lost.

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked.

Additional Information

This is specific to the Android Claude app driving a Remote Control session. The doubled /clear plus (no content) suggests the command is being submitted and echoed twice, and the session then never leaves its busy/loading state, which is what swallows the next prompt.

I found some related but different reports:

• anthropics/claude-code#68425 (/clear does not clear context on mobile) is about /clear being a no-op. In my case /clear does fire ((no content) is shown), but the session then hangs.
• anthropics/claude-code#63924 and #69606 are about slash commands from a remote device being routed to the model as plain text. Mine is not routed to the model. It renders as a real /clear and then the UI locks up.
• anthropics/claude-code#65462 is about typed text disappearing on mobile, but there the message is still sent. In my case the grayed-out input is never sent at all.

So the new part here is the stuck loading state after /clear that silently drops the next prompt until I close and reopen the window.