Launch support
Desktop-first help and troubleshooting
These are the launch-critical guides for installing desktop, connecting providers, making projects appear remotely, and recovering companion notifications or desktop availability.
Install desktop
Download the installer from the desktop download page, run it, then open Sifr Desktop and sign in. The first-run path should be sign in, connect a provider, attach a project, and start your first local session.
Connect Claude Code or Codex
If the desktop app does not detect a provider, make sure the CLI is installed on the same machine, the account is authenticated, and Sifr Desktop can see that local environment. Re-run the provider connection step from desktop onboarding after the CLI login completes.
Project not appearing remotely
The desktop must be online, signed in to the same Sifr account, and have remote access enabled for the project. Once the runtime inventory sync succeeds, the project should appear on web and mobile under your connected desktops.
Desktop offline
If a desktop-backed session shows offline, reopen the desktop app, confirm the provider is still connected, and check the runtime heartbeat or sync status. You can continue the same session in cloud only when that fallback is explicitly available.
Sync or relay failure
A relay issue usually means the desktop cannot reach the API, the account token expired, or the runtime lease went stale. Re-sign in on desktop, refresh the runtime, and verify that the project is marked remotely available again.
Notifications not working
Mobile push notifications require a physical device, permission acceptance, a valid Expo push token, and an authenticated session. If approval or desktop-offline alerts are missing, re-open the mobile app, re-enable notification permissions, and refresh your notification registration.