[Bug]: iOS does not show Monitoring status displayed on desktop and web

[etcircle]

Problem and reproduction

When the same thread shows Monitoring on desktop and web, the iOS app does not show a corresponding monitoring indicator. This makes it unclear whether the agent is still watching/waiting or has finished.

1. Use a thread that desktop/web currently labels Monitoring.
2. Open the same environment and thread in the iOS app.
3. Compare the thread status: desktop/web communicates monitoring, while iOS provides no equivalent indication.

Expected: iOS should visibly distinguish Monitoring from active Working and completed/idle states, consistent with desktop/web. Check both the thread list and open-thread presentation, and clear the indicator when monitoring ends.

Environment and source evidence

Observed with a Mac-hosted T3 Code environment; desktop version 0.0.38. The iOS app was recently installed/updated; its exact version/JS update is unconfirmed.

Upstream source inspected at 223ff4490f764a74ff911589e97b9bbcd595fee8:

• Web status resolution explicitly handles backgroundLiveness === "monitoring", separately from background subagents doing active work.
• Mobile status presentation has no Monitoring branch.
• Mobile thread-list v2 considers approvals, input and parent-session status, then falls back to ready; it does not consume background liveness.

These are source observations, not confirmation of the exact code installed on the phone.

Related issues checked

• [Bug]: Mobile looks idle while background subagents are still working #4962 covers mobile looking idle while background subagents are working. This report specifically covers the distinct Monitoring state for passive watch/wait activity.
• [Feature]: Mobile: sub-agent visibility parity — spawn indicator, Agents surface, and background liveness #6402 covers broader mobile subagent visibility and is closed.
• Missing Done presentation already has an open report, [Bug]: Mobile thread list never shows Done after a turn completes #4952. Done behavior has not been independently confirmed in this case and is not a second asserted bug here.

[juliusmarminge]

Triage

Confirmed presentation bug on current main (223ff4490). Desktop/web already distinguish Monitoring from Working; mobile never does.

backgroundLiveness is already on OrchestrationThreadShell (packages/contracts) and on the mobile thread shell. Web uses it in Sidebar.logic.ts / Sidebar.tsx (list label) and ChatView.tsx (open-thread “Monitoring” banner + Stop). Under apps/mobile there are zero references to backgroundLiveness or monitoring.

Status falls through to idle/ready:

• apps/mobile/src/features/threads/threadListV2.ts (resolveThreadListV2Status) — approvals, input, parent session.status, then ready
• apps/mobile/src/features/threads/threadPresentation.ts (resolveThreadStatus) — same; no Monitoring branch
• Open thread (use-thread-composer-state.ts, ThreadDetailScreen.tsx, floating-working-control.tsx) — parent session / latest turn only

This is shared mobile code (iOS and Android), not an iOS-only renderer bug.

Not a wash duplicate

• [Bug]: Mobile looks idle while background subagents are still working #4962 — same ignored field, but backgroundLiveness === "working" (active subagents). Web treats that as Working. This ticket is the distinct Monitoring watch/wait state. A fix that only maps "working" → Working would leave this open.
• [Bug]: Mobile thread list never shows Done after a turn completes #4952 — missing Done. Not asserted here.
• [Feature]: Mobile: sub-agent visibility parity — spawn indicator, Agents surface, and background liveness #6402 — closed broader Agents/liveness request. feat(mobile): subagent visibility with agents sheet and liveness #6616 would have added mobile monitoring and was closed unmerged. fix(web): show a thread's completion when a watch loop is still live #7655 notes mobile still does not surface backgroundLiveness.

Suggested fix

Consume thread.backgroundLiveness in both list resolvers and the open-thread indicator, matching web:

• "working" → Working (also [Bug]: Mobile looks idle while background subagents are still working #4962)
• "monitoring" → Monitoring (calm, no pulse — this ticket)
• null → current ready/idle

No contract or server change required. Pin with tests: settled parent + "monitoring" vs "working" vs idle.

Labels: bug, accepted, via-triage (remove needs-triage)