Platform support and limitations
Check host requirements and the limits that matter for remote and unattended work.
Updated 2026-10-29
Host platforms
| Platform | Installation target | Platform-specific limits |
|---|---|---|
macOS | Apple silicon with Git | Notification and awake locked-screen behavior still need live acceptance evidence |
Windows | x64 with Git for Windows | Keep-awake, screen-lock detection, and Wi-Fi inspection/auto-join unavailable |
Linux | Desktop x64 with systemd and Git | Same unavailable controls as Windows; the host service stays up after logout |
Windows ARM64 is not a published runtime target. Linux provider bundles require glibc; OpenCode x64 requires AVX2 unless the baseline build is bundled. A native Linux folder picker depends on a supported desktop dialog tool; a host path can be entered directly when the picker is absent.
Remote and unattended work
The host must stay reachable for a phone to control it. On Linux, installation enables the user service to keep running after the last logout, including when an SSH connection closes. Your system may ask for account authorization when Farero enables this setting.
macOS has a keep-awake setting for active agent work. Do not treat it as proof of notification delivery, closed-lid operation, or completion while the screen is locked in your environment.
Verification limits
The implementation targets core hosting, providers, workspaces, and private access across these platforms. Real Windows and Linux provider turns, workspace lifecycle, login persistence, and phone access have outstanding acceptance checks in the current source records. Notification delivery, tap routing, and update activation also need real-device evidence.
SIP calling is deferred. Cursor is not supported. See Troubleshooting for collecting a useful failure report.