Mobile client shows infinite loading spinner instead of an error when the session runner has died
Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 17, 2026
Observed behavior: A session started via the web UI responded normally until a certain point, then its runner process terminated (root cause not conclusively determined). The linked mobile client then showed a permanent loading spinner instead of an error or "connection lost" state.
Expected behavior: When a runner process has actually terminated, the client should show an error state promptly, not indefinite loading.
Note on evidence: Same as issue 3, no raw log excerpt available (capture ends before the incident). Based on manual observation during a reproduction test.
Environment: Session started via web UI (claude.ai/code), accessed/continued via mobile app.