One control plane, more places to operate it#
Desktop and mobile are projections of the same governed runtime. They do not create separate policy, evidence, or approval systems.
| Surface | Current role |
|---|---|
| Desktop | Tauri shell for authenticated cloud routes, device-bound auth storage, updater wiring, and sidecar-supervised local runtime work |
| Mobile | Expo app for Sidekick chat, approvals, jobs, operations inbox, widgets, voice, notifications, and release-candidate verification |
Desktop status#
The desktop path now has:
- a Tauri 2 shell with a Next renderer sidecar
- route-parity smoke coverage for authenticated cloud pages
- device-bound refresh-token storage through Stronghold and OS keychain
- auto-updater wiring and signing-channel setup
- a v2 runtime sidecar foundation with IPC, spawn supervision, sandbox policy, and model-bridge work in progress
Desktop is useful as a governed operating surface and local-runtime container. It is not a separate product truth from the cloud control plane.
Mobile status#
The mobile app now tracks the May 2026 product shape more closely:
- Sidekick envelope and gate-resolver widget conformance
- operations inbox and approval drawer surfaces
- Jobs artifact ledger and detail rail
- voice transport and post-deploy smoke automation
- release readiness work around Expo, EAS, TestFlight, and iOS 26
The Android submit lane and some store-release items remain explicit release readiness work. The mobile app should be described as active native release work, not as already broadly store-launched.