Limitations
What Mobile Presence does not do.
Not implemented
The phone PWA is not an independent execution surface — it does not run the Coding Runtime, connect to connectors on its own, or take actions your desktop session isn’t already driving. It extends and remotely controls a desktop session; it does not replace one.
How it works
What you see
- Pairing, trusted devices, presence, notifications and approvals on your phone.
- Clear status: active, paired, waiting for approval or disconnected.
What PawOS does
- Pairing creates a trusted link between your phone and your desktop.
- Your desktop stays in charge of files, commands, installs and apps.
- Approvals on your phone respond to real pending requests from your desktop.
Permissions
- Pairing a phone never gives it direct access to your files, terminal, connections or deployments.
- An approval from your phone still goes through the desktop’s own checks.
Records
- Presence and approvals are tied to real task and approval state on your desktop.
Good to know
- Mobile works alongside the desktop app; your desktop needs to be online.