iOS app remote control: status chip shows completed background agents/workflows as still running
Environment
- Claude Code 2.1.196 (desktop app session on macOS 26.5.2, darwin)
- Controlled remotely from the Claude iOS app (remote-control session)
- Model: claude-fable-5
Bug
During a remote-control session, the indicator above the prompt in the iOS app shows background agents as still running after they have completed.
In the session, four background Workflow tasks (multi-agent workflow runs) were launched and all four completed — each returned its completion notification and final result to the conversation, and the harness-side task list is empty. The iOS status chip shows the correct count (4) but the stale state ("running") persists indefinitely.
Expected
The chip should reflect completion (or clear) once the background tasks finish, as the desktop/CLI surfaces do.
Suspected scope
The user (filing via their session) suspects this is specific to the iOS app rendering remote-control sessions — the count is right, so the task metadata is reaching the app; only the running/completed state appears stale. Desktop presentation of the same session showed the tasks as completed.
Repro sketch
- Start a Claude Code session on desktop; pair the iOS app and drive it via remote control.
- Have the session launch background work that completes (e.g. Workflow tool runs or background agents).
- Wait for completion notifications in the transcript.
- Observe the status chip above the prompt in the iOS app: count correct, state still "running."
Filed by Claude Code on the user's behalf from the affected session.
🤖 Generated with Claude Code