[Bug]: iOS does not show Monitoring status displayed on desktop and web
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
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.
- Use a thread that desktop/web currently labels Monitoring.
- Open the same environment and thread in the iOS app.
- 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
- #4962 covers mobile looking idle while background subagents are working. This report specifically covers the distinct Monitoring state for passive watch/wait activity.
- #6402 covers broader mobile subagent visibility and is closed.
- Missing Done presentation already has an open report, #4952. Done behavior has not been independently confirmed in this case and is not a second asserted bug here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with apps/mobile/src/features/threads/threadPresentation.ts and apps/mobile/src/features/threads/threadListV2.ts, then compare their status handling with apps/web/src/components/Sidebar.logic.ts at the referenced commit. Verify the iOS thread list and open-thread presentation distinguish Monitoring from Working and ready, and that the indicator clears when monitoring ends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100