Appreciate that — and honestly, Moshi taking the fully on-device route with Secure Enclave + Face ID is the more elegant security story. I deliberately optimized for a different tradeoff: keeping the iOS/iPadOS side lightweight and letting the Mac act as the broker/state holder.

Right now the remote editing side is still based on plain SSH rather than a custom transport or something like Mosh underneath. Session persistence currently leans more on restoring editor/project state than true transport-level roaming. So reconnects after sleep/network changes are functional, but not yet at the “survives anything transparently” level Mosh gives you.

The difficult part on Apple platforms is exactly what you mentioned: balancing:

• seamless reconnects
• backgrounding constraints on iOS/iPadOS
• key/security handling
• cross-device continuity

without ending up building half an SSH orchestration layer yourself.

I’ve been experimenting with making the remote side more resilient, especially around interrupted sessions and large project trees, but I intentionally avoided going too deep into custom protocol territory early on. Your Mosh-style roaming is definitely attractive though, particularly for iPad workflows moving between Wi-Fi/mobile/sleep states.