Most mobile AI coding workflows eventually hit the same wall.
tmux keeps the process alive. SSH lets the phone attach. Remote desktop can show the whole screen. None of that means the phone is a good control surface.
On a phone, the common loop is much smaller:
- see which Codex, Claude Code, or shell session is alive
- read the last meaningful output without parsing a full terminal wall
- send a short nudge back into the same running process
- approve or reject a blocked action
- interrupt when the agent is clearly going wrong
- hand the context back to the desktop without creating a second history
That is the gap I built Faryo for.
Faryo is an open-source phone/browser workbench for tmux-backed AI coding sessions. The local tmux session stays the source of truth. Codex CLI, Claude Code, or a plain shell keeps running on the host. The phone/browser layer is deliberately thin: compact output, short input, approve/interrupt, and handoff.
It is not a remote desktop. It is not a cloud IDE. It is not another AI chat thread.
The narrow promise is: keep the same live terminal session, but stop forcing the phone to behave like a full terminal.