Android and Linux are the initial platform scope, subject to physical-device qualification. Get the Linux archive from Downloads when a release is available and check its SHA-256. Keep ophio and computer-mcp from the same archive together with the licence notices and SBOM.
Linux
You need x86_64 Linux with glibc 2.39 or later. Ubuntu 24.04 is the baseline. PipeWire and the applicable Wayland or X11 libraries must be installed.
If startup reports a missing libpipewire-0.3.so.0 or libxkbcommon.so.0, install your distribution’s packages. On Ubuntu these are libpipewire-0.3-0t64 and libxkbcommon0. On Arch they are libpipewire and libxkbcommon.
Extract the archive and run its installer from a terminal as your normal user, not root:
sh install.shThe installer puts the programs in your user installation and links ophio into ~/.local/bin. It also installs notification icons in your user icon theme and, when included, keeps ophio.apk in ~/.local/opt/ophio/app. It does not install a graphical companion window; setup and service controls run in the terminal. A first terminal install starts guided setup. You can also start it yourself:
ophio setupIf the shell cannot find ophio, check its PATH. On Ubuntu, logging out and in may apply the user-bin path. To add it for the current shell:
export PATH="$HOME/.local/bin:$PATH"Add that export to your shell configuration if needed. Run setup from your graphical desktop session.
Guided setup
Setup walks through keeping Ophio running, network reach, agent sign-ins, installing and pairing the phone, optional features and a readiness check. It remembers completed steps. You can skip a step and return with ophio setup. Running it again does not undo unchanged choices. Bare ophio resumes a new or incomplete setup.
Setup’s Agents step offers to install and sign in to missing agents, choose a default for new projects, and optionally keep installed Claude Code and Codex up to date. That last choice maintains separate managed copies; it does not update Ophio. See agent updates.
Use ophio setup --plain for plain terminal output or ophio setup --still to avoid animated output. Setup can start a helper agent, but those helpers use standard approvals, not the phone’s default permission-bypass policy. They cannot complete owner sign-ins, grant pairing permission or enter secrets for you. See Agents, skills & launchers.
Install and sign in to the native Claude Code or Codex CLI for the agent you want to use. Codex requires version 0.153.2 or later and its bundled code-mode helper. Run:
ophio --version
ophio doctorRead each unavailable capability and its remedy. Pairing does not make missing agents, speech models or desktop permissions available.
Keep Ophio running
Setup can install the per-user service. To do it manually, first stop a manually running instance, then run from the graphical session:
ophio service install
ophio service statusThis is not a system service. A desktop without graphical-session.target can use the fallback target, but may start Ophio without desktop access. Installing from outside the desktop can also omit needed session variables. Reinstall the service from the graphical session rather than adding elevated permissions.
For a manual foreground session, use ophio run. Leave it running and use another terminal for pairing or checks. See the Linux package instructions for startup details.
Windows preview
Windows has partial Windows 11 virtual-machine evidence. It is not physically qualified for the initial release. Do not treat the preview package as a supported first-release install.
The preview uses an ordinary, non-administrator PowerShell in the extracted folder:
.\ophio.exe setup
.\ophio.exe doctorKeep both executables together. In an ordinary-user terminal, .\ophio.exe service install starts Ophio immediately and registers future logon startup. From an administrator terminal it only registers startup, to avoid launching Ophio as administrator; it starts at the next login.
The preview is unsigned. Review Windows download warnings and private-network firewall requirements in the Windows package instructions. Never enable broad public-network access just to make pairing work.