[BUG] Remote Control: teammate/subagent permission prompts not forwarded to mobile (iOS) — unfixed since #24694

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?

Bug Description

Permission prompts from subagents / Agent Team teammates are not forwarded to Remote Control on mobile (iOS app), even though they are visible and actionable from the local laptop terminal.
This makes it impossible to approve or deny a teammate's tool call while away from the machine — the whole point of Remote Control.

This is not a new report. It was already filed as #30012, closed as a duplicate of #24694. #24694 is also closed, with no shipped fix or linked PR. Re-opening here because the underlying bug is still live on the current release and the closure chain has no fix attached to it.

Environment

• Claude Code version: 2.1.223 (latest as of Aug 5, 2026)
• Platform (laptop/host): [macOS/Windows/Linux + version]
• Remote client: Claude iOS app, v1.260721.0 (build 29849567768)
• Agent mode: Agent Teams (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1)
• Remote Control mode: /remote-control.

Steps to Reproduce

1. Start a Claude Code session on the laptop with Agent Teams enabled (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1).
2. Start a Remote Control session (claude --remote-control or /remote-control).
3. Connect from the Claude iOS app.
4. Spawn a team / have a teammate agent attempt a tool call that requires permission (e.g. an unapproved Bash command or file write).
5. Observe the iOS app while the teammate is blocked waiting for approval.

Actual Behavior

• The Team Lead's own prompts show up fine on mobile and can be approved there.
• Teammate/subagent prompts show only in the local terminal / tmux sub-pane.
• The iOS app gives no indication a teammate is blocked — it just silently stalls until someone opens the laptop and answers the prompt locally.

Expected Behavior

The permission prompt from the teammate sub-pane should be forwarded to Remote Control and be approvable/deniable from the mobile client, the
same way Team Lead (main pane) prompts already are.

Why the Duplicate Closure Doesn't Resolve This

• #30012 (opened Mar 2, 2026) was closed as a duplicate of #24694.
• #24694 is itself closed, with no fix, changelog entry, or PR reference attached.
• As of Claude Code v2.1.223 (Aug 5, 2026) and iOS app v1.260721.0, the behavior described above still reproduces — five months and 200+ point releases after the original report.
• Filing fresh so this doesn't get silently closed into the same dead-end chain again. Happy to have this merged into an actively-tracked issue if one exists, but please link the actual fix/PR when doing so rather than another closed duplicate.

Impact

This defeats a core use case of Remote Control: stepping away from the laptop while Agent Teams work continues. Any team run with more than the lead agent effectively requires staying near the host machine.

What Should Happen?

Should be prompted to accept or deny.

Error Messages/Logs

Steps to Reproduce

1. Start a Claude Code session on the laptop with Agent Teams enabled (CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1).
2. Start a Remote Control session (claude --remote-control or /remote-control).
3. Connect from the Claude iOS app.
4. Spawn a team / have a teammate agent attempt a tool call that requires permission (e.g. an unapproved Bash command or file write).
5. Observe the iOS app while the teammate is blocked waiting for approval.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code v2.1.223

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_