Snailflyer/faryo

Faryo feels like a tool built from a real workflow pain: you have a long-running Codex, Claude, or shell session in tmux, you step away from the desk, and you want to check output or send one short instruction without starting a new chat or exposing a full remote desktop. That is a useful, concrete problem, and the project explains it well.

The strongest part is the architecture. Keeping the Owner service local and loopback-first, while putting public access through Gateway, makes the security model easier to understand. The README is also unusually clear about what Faryo is and what it is not. It covers install steps, supported paths, session convergence, handoff packages, runtime state, packaging, and deployment rules without overselling the project.

There are still some early-project rough edges. The repo would benefit from a real short demo near the top of the README, because “same live session from phone and desktop” is much easier to trust when you can see it. The open issues for a GIF and a redacted handoff walkthrough are the right priorities. I’d also like to see regular CI for smoke checks and a few focused tests around auth, file access, private URL rejection, and session routing. Those areas matter because this tool can control a real local terminal session.

Overall, Faryo is a promising and practical developer tool. It has a clear niche, good docs, release packages, a license, contribution notes, and a security model that shows the maintainer is thinking carefully. The next step is less about adding features and more about proving the workflow visually and backing the safety claims with automated checks.