How does it actually work?+
Two apps: a Mac companion in the menu bar, and an iOS client. They pair through Sign in with Apple, then open an end-to-end encrypted WebRTC connection between your iPhone and your Mac. On the same Wi-Fi the connection is direct host-to-host. Off your local network, ICE negotiates a NAT-traversal path; if direct P2P is blocked, the apps fall back to a Cloudflare TURN relay. Either way the media, video, touches, terminal, build commands, is protected by DTLS-SRTP, and only your iPhone and your Mac hold the keys.
Do I have to stay on the same Wi-Fi?+
No. Xtend reaches your Mac from anywhere on the open internet, on both tiers, remote access is not the paid feature. On the same network the path is direct; outside it, ICE finds a way through, with an encrypted relay as fallback.
Are the coding agents included?+
No, and that's deliberate. Xtend drives the CLIs you already have installed on your Mac. Claude Code, Codex, with your own keys and your own subscription. Nothing runs through us: the CLI executes locally and the answer is streamed back to your phone.
Does it replace Xcode?+
No. Xcode does the actual building. Xtend drives it from your phone. Think of it as a remote control for the parts of Xcode you'd want when you're not at the keyboard: trigger a build, watch it run, peek at the Simulator, drop into a terminal.
Will my data leave my machine?+
Sign in with Apple is required so the iPhone can find the Mac that belongs to your account, that single auth handshake goes to our server. Beyond that, your Simulator stream, terminal data and build commands flow directly between your iPhone and your Mac over end-to-end DTLS-SRTP; our signaling server only relays the initial WebRTC handshake, not media. When you're off your local network, a Cloudflare TURN relay forwards encrypted bytes only, it can never decrypt your session. The only telemetry is crash reporting and usage counters, keyed to a random install ID before you sign in and to your Apple user identifier after, never to your files or terminal contents. A single toggle, on the iPhone and on the Mac, turns all of it off. Details in the privacy policy.
Why isn't the Mac side on the App Store?+
The Mac companion reads your Xcode projects, drives xcodebuild and captures the Simulator window. Those operations sit outside the Mac App Store sandbox, so the Mac app is distributed directly from this site. The iOS client ships through the App Store as normal.
What happens when I hit a daily limit?+
Only the metered part stops. If you run out of Simulator minutes the video pauses, your chat, terminal and builds keep working, and the session stays connected. Everything resets the next day, or you can upgrade to remove the ceiling.
What's coming next?+
Multiple Macs per account, session recordings, and team accounts are the next things on the list. Dates aren't promises, software ships when it ships.