[BUG] Remote Control: "Always allow" permission from Android app breaks tool calls

Open 💬 13 comments Opened Apr 9, 2026 by Fefo83

Summary

When approving a tool call from the Claude Code Android app via /remote-control with "always allow", the tool call fails with "internal error". Using "allow once" works normally. Approving from the local terminal works in both modes.

Environment

  • Claude Code 2.1.98
  • WSL2, Ubuntu 24.04.3 LTS, kernel 6.6.87.2-microsoft-standard-WSL2
  • Android app (latest)

Repro

  1. Start a Claude Code session in WSL terminal.
  2. Run /remote-control and connect from Android app.
  3. From the mobile app, prompt Claude to call a tool (e.g. WebFetch https://www.4foreverything.com/en).
  4. When the permission prompt appears, choose "always allow".
  5. Tool call returns [Tool result missing due to internal error] or session appears to hang.

Expected

Same behavior as "allow once" — the tool call executes and returns a result.

Actual

Tool call fails with internal error. Retrying with "allow once" works on the same URL/prompt.

Notes

  • Only happens when the prompt originates from the mobile remote-control channel. Local terminal prompts work with both permission modes.
  • May be related to a render-refresh issue: the terminal TUI sometimes doesn't redraw until a local keypress, which makes failures look like hangs.

View original on GitHub ↗

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