[BUG] Remote Control hangs: tool calls drop with "internal error" and permission prompts not forwarded

Resolved 💬 3 comments Opened Apr 17, 2026 by rousegordon-ops Closed Apr 20, 2026

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?

Two issues when using Claude Code via Remote Control from the mobile app:

  1. Long-running tool calls silently fail

When controlling a session remotely, tool calls that take more than a few seconds frequently fail with "Tool result missing due to internal
error." The same commands succeed reliably when run locally or with run_in_background: true. Examples that fail: railway up (file upload +
deploy), complex piped shell commands. Simple/fast commands like curl or git status work fine. Likely a timeout or connection-stability
issue in the relay layer.

  1. Permission prompts not forwarded to remote client

When a tool call triggers a permission prompt on the host machine, the remote client shows no indication — the session just appears hung.
The user has no way to approve or deny the prompt remotely. If not near the host machine, the session is effectively stuck. Workaround:
pre-allow common operations in ~/.claude/settings.json permissions.

Environment:

  • Host: macOS (Darwin 24.6.0), Claude Code CLI
  • Remote client: Android, Claude mobile app
  • Model: Claude Opus 4.6

What Should Happen?

It shouldn't hang all the time when I'm using remote control

Error Messages/Logs

Steps to Reproduce

Deploy a web app on railway using remote control from android phone.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.112

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗