Problem
On connect/reconnect failure, sessionManager stores runtime.error (e.g. "Failed to reconnect."), but SessionView (the React-facing shape) only exposes meta, status, timeline — error is never included, so the message is invisible. The only signal is the status dot turning to "Offline".
Suggested fix
Expose error on SessionView and render it (e.g. an inline banner) so users know why a session is offline and can act.
Where
mobile/src/lib/sessionManager.ts (SessionView ~37–41; error set ~166–169, ~366–368).
Filed from a UI research sweep of the Helm mobile app (landing + live demo session) using Playwright + full source review, cross-referenced against Claude, ChatGPT, GitHub Copilot Chat, and Codex/Claude Code UIs.
Problem
On connect/reconnect failure,
sessionManagerstoresruntime.error(e.g. "Failed to reconnect."), butSessionView(the React-facing shape) only exposesmeta,status,timeline—erroris never included, so the message is invisible. The only signal is the status dot turning to "Offline".Suggested fix
Expose
erroronSessionViewand render it (e.g. an inline banner) so users know why a session is offline and can act.Where
mobile/src/lib/sessionManager.ts(SessionView~37–41; error set ~166–169, ~366–368).Filed from a UI research sweep of the Helm mobile app (landing + live demo session) using Playwright + full source review, cross-referenced against Claude, ChatGPT, GitHub Copilot Chat, and Codex/Claude Code UIs.