Claude Code Remote Control Reply Missing? Refresh Before Resending

If Claude Code Remote Control accepts your message but shows no reply, do not resend the prompt immediately. Wait for the local turn to finish, confirm the local Claude process is still connected, then refresh the browser once. If the complete reply appears after refresh, treat the turn as completed and audit its tool calls or file changes before sending anything again. Resending first can duplicate edits, comments, deployments, or other side effects that already happened while the remote view was blank.

This is a workaround for an open rendering issue, not a confirmed fix. Claude Code issue 85240 reports that every reply stayed invisible on iPad Safari, iPad Chrome, and macOS Safari until a manual refresh. A second reporter reproduced the failure on Firefox ESR while Chromium on the same machine rendered normally. The issue remains open, and its discussion narrows the symptom to the remote client without proving one universal browser or framework root cause.

Separate a Hidden Reply From a Disconnect

Two Remote Control failures can look similar but need different recovery paths.

Anthropic documents Remote Control as a window into a Claude Code process that continues to run on your machine. The browser and local terminal share a stored session transcript, while execution and filesystem access remain local. In the reported failure, a refresh reconstructed the complete reply. Together, those observations are strong evidence that the affected turn finished, but they do not identify whether decoding, state reduction, subscription, or rendering failed.

For startup, authentication, or reconnection errors, use the broader Claude Code Remote Control disconnect guide. This guide covers the narrower case where a finished reply exists but the live view stays blank.

Recover the Hidden Reply Safely

Start at the machine running Claude Code if you can access it.

1. Stop typing in the remote prompt. Do not use a second message as a refresh trigger.

2. Check whether the local terminal is still producing output or showing a permission request.

3. Wait for the local turn to finish. If you cannot see the host, wait at least as long as the same task normally takes.

4. Confirm the connection indicator still shows /rc active in the interactive terminal when that indicator fits the terminal width.

5. Refresh the remote page once with the browser's normal reload command.

6. Read the complete reconstructed reply from the beginning, including every tool result and claimed side effect.

7. Verify those side effects independently before sending a follow-up.

For a coding task, inspect the real repository state:

git status --short --branch
git diff --check
git diff --stat
git diff --no-ext-diff

For a provider action, check the provider-owned record instead: the issue comment, document URL, deployment ID, message timestamp, or other unique result. Do not repeat a write merely because its confirmation was hidden.

If refresh reveals a permission dialog rather than a reply, answer it only after checking the local terminal and the intended operation. A forwarded dialog can expire, and the absence of visible output is not approval.

Run One Harmless Rendering Probe

After preserving the affected turn, test the same session with a prompt that cannot change state:

Reply with exactly: remote render probe received
Do not use tools and do not change any state

Record four facts:

• whether the reply appeared without refresh;

• whether it appeared after one refresh;

• browser, browser version, operating system, and Claude Code version;

• whether the same session rendered correctly in a second browser.

One commenter on issue 85240 reproduced the blank view in Firefox Troubleshoot Mode while Chromium on the same Debian machine worked. That makes an alternate-browser check useful, but it does not prove Chromium is a permanent fix for every environment. Use it as an isolation step, not as a reason to clear all browser data or rebuild the session.

Do not test with a deploy, merge, file edit, external message, or approval. The probe should be safe to receive twice if the client later replays it.

Confirm Delivery Without Exposing the Transcript

If you are comfortable with browser developer tools, preserve a minimal network observation before refreshing:

1. Open the Network panel.

2. Select the active WebSocket connection.

3. Send the harmless probe.

4. Check whether a new incoming frame arrives while the page remains blank.

In the public issue, one reporter saw a complete incoming frame, no console error, and no rendered reply until reload. That observation narrows their case beyond a generic network disconnect. It does not establish the same boundary on your machine.

Do not publish frame contents, the full transcript, session URLs, credentials, repository paths, customer data, or tool outputs. A timestamp, browser version, frame-arrived yes/no result, and redacted screenshot are usually enough for a useful issue update.

If no frame arrives and the local terminal reports a dropped connection, stop treating the problem as rendering. Follow Anthropic's documented reconnection path instead.

Update One Variable at a Time

Issue 85240 was still open when this guide was researched on August 10, 2026. Before retesting:

claude --version
claude doctor

Update Claude Code through the supported installation method you already use, restart once, and repeat only the harmless probe. Then test one browser change at a time:

1. affected browser in its normal mode;

2. the same browser with extensions disabled or its troubleshooting mode;

3. one current browser with a different engine;

4. a fresh Remote Control session only if the existing session still fails.

Changing the Claude Code version, browser, extensions, network, and session at once destroys the comparison. Keep the smallest reproduction that distinguishes a missing frame from a received-but-unrendered reply.

Monitor the Open Issue With Aident Loadout

You can check the upstream issue without copying a GitHub token into the remote prompt. Start with:

Follow https://aident.ai/SETUP.md

Then ask your agent:

Check Aident Loadout authentication and Vault status. Discover the current read-only GitHub issue Action, inspect its schema, and preflight a lookup for anthropics/claude-code issue 85240. If it is valid and free, execute only that read Action. Return state, updated time, comment count, labels, title, and canonical URL. Do not comment, react, edit, close, label, or create anything.

The measurable result is one current issue-state record with zero GitHub writes. If the issue closes or Anthropic's changelog names a rendering fix, rerun the harmless probe before returning to side-effecting Remote Control work.

Set up Aident Loadout and monitor the Remote Control rendering issue.

Sources

• Claude Code issue 85240: Remote Control responses never render until refresh

• Issue 85240 comment: complete WebSocket frame arrives but the UI stays blank

• Claude Code issue 34581: Remote Control content stops appearing while the CLI continues

• Anthropic: Claude Code Remote Control

• Anthropic: Claude Code troubleshooting

• Aident: How to fix Claude Code Remote Control disconnects

Refresh this guide when issue 85240 changes state, Anthropic documents a client-rendering fix, or Remote Control changes its transcript, connection, or browser-support contract.