Remote/mobile: 'Approve once' does not stick — identical permission prompt re-appears in an endless loop

Environment

• Claude Code driven remotely from the Android mobile app (remote control session to a Linux desktop)
• Session model: claude-opus-4-8
• Observed repeatedly on 2026-06-07, ~4 separate occurrences in one session

Bug

When a Bash permission request reaches the mobile app, 'Approve once' is the only option offered (no 'always allow' from remote). Tapping it appears to succeed — returning to the chat shows the agent continuing to work. But on leaving and re-entering the session list, the exact same approval card is shown again, and this repeats indefinitely (rinse and repeat) for the same command.

Agent-side correlation

Each time this happened, the corresponding tool call on the agent side returned:
[Tool result missing due to internal error]
— so the approval seems to be lost between the mobile approval and the tool execution, leaving both sides confused: the user keeps approving, the agent never reliably receives the result.

Impact

Long-running sessions are effectively unusable from the phone. The user (running 4-5 concurrent sessions) was interrupted repeatedly and ultimately had to build a custom PreToolUse auto-approve hook to bypass the permission system for known-safe command patterns — which defeats the purpose of the permission UX.

Steps to reproduce

1. Start a session on a desktop machine, attach via the mobile app (remote control).
2. Have the agent run a Bash command not covered by permissions.allow.
3. Approve via 'Approve once' on the phone.
4. Navigate away and back: the same approval card re-appears; the agent-side tool result is lost.

(Filed via Claude Code on the user's behalf, at the user's request.)