Repository navigation
Mobile companion: PWA with lock-screen progress, approve-from-phone, offline queue #287
Description
Inspired by Cursor iOS (Live Activities on the lock screen, remote-control with keep-awake toggle), Happy Coder (E2E relay, offline-first command queue), and Claude Dispatch (one persistent cross-device thread).
Builds on #151 (QR pairing) and #245 (headless server): a companion PWA (no native app needed — web push + installable) showing per-thread progress as persistent notifications, permission prompts approvable from the phone with 'remember for this session' granularity, and phone-originated messages as durable queued items delivered when the desktop reconnects. Relay traffic end-to-end encrypted with keys from the QR exchange (Happy's zero-knowledge posture — marketable for an app holding five providers' sessions). One persistent cross-device thread per Solenta thread, with explicit handoff semantics when both devices are attached.
Activity
currentbits commentedon Aug 17, 2026
User-pain research (round 6) sharpens the design: the corroborated division of labor is 'phone for intent + approvals, desktop for review' — nobody wants to write code on glass, and even Happy Coder fans accept view-only diffs. Notification correctness is existential: the two ways to die are silently dropped messages (make the relay replay-tolerant) and notifications that work in test paths but not the real permission flow. Anthropic's own data: users accept 93% of permission prompts, so notify ONLY on judgment-required events. Ship voice input early — multiple tools independently found users give richer prompts by voice. And relay via the structured protocol, never terminal scraping: Omnara's v1 died parsing CLI output that changed every release.
currentbits commentedon Aug 17, 2026
Research note (Fyxer's distribution trick): write triage state into GitHub-native artifacts (labels, draft comments) so the GitHub mobile app becomes a free companion surface before the PWA exists.
currentbits commentedon Aug 18, 2026
From the opencode doc-mine: mDNS multi-instance discovery (--mdns) + opencode attach — headless servers advertise themselves on the LAN and the web UI has a See Servers page. Phone-discovers-desktop without manual ports: the cheapest pairing bootstrap for the mobile companion.
currentbits commentedon Aug 18, 2026
Round 19 validation: Cursor's mobile arc is now fully shipped and it matches this issue's scope almost point for point:
The one piece beyond #287's current scope: Remote Control (the phone steers an agent running on the desktop, not just cloud sessions). For local-first Solenta that is actually the easier architecture: phone PWA talks to the Solenta orchestrator on the user's own machine over the tailnet/LAN, no cloud relay needed. Bump this issue's priority signal accordingly.
currentbits commentedon Aug 18, 2026
Round 25 demand note: "Mobile version of OpenCode" (anomalyco/opencode#10288) keeps collecting votes, Codex users ask for voice transcription in the IDE extension (openai/codex#3000, 34 comments), and Cursor's iOS/iPad apps shipped with Live Activities (earlier comment). The supervision-from-phone pattern has demand from every direction now.
currentbits commentedon Aug 18, 2026
Round 27 intel: Orca's mobile companion (Expo, beta) is the most complete shipped reference: pairing is a paste flow with Keychain-backed device tokens (no account required for the pairing itself), and the phone surface includes terminal text selection/copy/paste, an account switcher, live rate-limit usage, source control with PR checks, and workspace creation parity with desktop. Two design points for Solenta's PWA: (1) the pairing flow is paste-a-token, not scan-QR or sign-in, which fits a tailnet/LAN deployment; (2) rate-limit/quota visibility on the phone is part of the supervision surface, users check "can I keep going" from the couch.
currentbits commentedon Aug 18, 2026
Round 29 intel: intentic's remote-access model is the most local-first-compatible design seen yet: the browser connects straight to your own machine (laptop, desktop, VPS), and their cloud platform stores only your identity and your sandbox's URL. Nothing else transits them. Their tagline: "You delegate. They work. You approve. Nothing happens out of sight." For Solenta's PWA this validates the direct-connection architecture (tailnet/LAN, or an outbound-only tunnel like intentic/Cloudflare for NAT cases) over any relayed model, and it shows the pitch writes itself: remote control without a middleman seeing your code.
currentbits commentedon Oct 19, 2026
Not planned (board cleanup 2026-10-19). Solenta Web with QR pairing and a Tailscale helper (#1512) already puts the full UI on a phone. PWA, push and offline queue are not planned.