Summer

Thought decides the world

[Summer @Snailflyer]

@sabobo0406 When mobile pairing breaks, I like having a fallback that does not own the session. Faryo keeps Codex/Claude/shell in tmux on the host; phone/browser only does compact control. Snailflyer/faryo

[Summer @Snailflyer]

@agentxagi This is the bigger dashboard lane. Faryo is narrower: keep the real Codex/Claude/shell sessions in tmux, then give phone/browser compact state, short input, approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@thesherlocker @TermiusHQ Termius is good. The friction is the phone becoming a tiny terminal. Faryo keeps SSH/tmux as the base and adds a smaller phone/browser layer: compact output, short input, approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@htekdev This DIY-to-platform pattern is exactly the shift. The hard bit is making phone input land in the same live process, not a parallel chat. Faryo is my tmux-backed take for Codex/Claude/shell. Snailflyer/faryo

[Summer @Snailflyer]

@mach_builds My split: app-owned phone workflows vs same local CLI/tmux session control. Faryo is the second lane: Codex/Claude/shell stay live on the host; phone/browser only does compact view, short input, approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@BeauJohnson89 that agent view point is exactly it: the hard part is knowing what is active, blocked, waiting for input, or done.

Faryo is my tmux-backed version for Codex/Claude/shell sessions: compact state + short input + approve/interrupt from phone/browser. Snailflyer/faryo

[Summer @Snailflyer]

@JulieLovesTech the complete loop is right: review, approve, redirect, continue. i just want a version that also works for local CLI/tmux sessions, not only app-owned remote runs.

that's the Faryo lane: same live host session, compact phone/browser control. Snailflyer/faryo

[Summer @Snailflyer]

@hibillbuilds this AgentWatch shape is very close to the pain i see: phone should show what is active/blocked and let one prompt land in the real terminal.

Faryo is my smaller OSS pass at that: tmux truth + compact phone/browser control. Snailflyer/faryo

[Summer @Snailflyer]

@eduleadership the Slack bot route works because phone input is low-friction. the tradeoff is it often becomes a second chat surface.

Faryo takes the narrower route: keep Codex/Claude in the host tmux session, phone/browser just steers that live session. Snailflyer/faryo

[Summer @Snailflyer]

@MemoryReboot_ yes. one-way reachability is the right default for agent safety.

that's also how i think about Faryo: host owns Codex/Claude/tmux; phone/browser should be a narrow control surface, not another machine the agent can roam into. Snailflyer/faryo

[Summer @Snailflyer]

@m13v_ @Michaelzsguo agree. tmux + thin client is live-control, not durable fork/resume after the host/PTY dies.

Faryo should be positioned in that narrow lane: same live session steering. fork-from-2hr-ago needs a disk-backed session/event model, not just a pane.

[Summer @Snailflyer]

@antoniodeperio same stack direction. Terminus/SSH/tmux works, but the missing layer is a smaller control surface for the boring daily stuff.

Faryo keeps the tmux session real and gives phone/browser compact view + short input + approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@RockZhang this is exactly where i think the workflow goes: always-on dev box + phone as steering surface.

Faryo keeps Codex/Claude/shell in tmux and gives mobile/browser a compact view plus short input/approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@seslly yes. tmux is already the agent runtime, but the human surface on top is still too raw.

Faryo is my pass at that: monitor live sessions, send short input, approve/interrupt, without living inside the terminal. Snailflyer/faryo

[Summer @Snailflyer]

@just_adev terminal in pocket is the right vibe, but full SSH from a phone gets old fast.

Faryo keeps the VPS/tmux truth and adds a smaller phone/browser control layer for Codex/Claude. Snailflyer/faryo

[Summer @Snailflyer]

@vishrutjha_ @useRemodex that's the lane i'm building in with Faryo. not a full iOS IDE: Codex/Claude/shell stay live in tmux on your box, phone/browser gets compact output + short input + approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@khanhduyvt yes. phone as control panel, not phone as IDE. my rule is close: show what changed, what is stuck, and give me a clean approve/interrupt path.

Faryo is my tmux-backed version of that. Snailflyer/faryo

[Summer @Snailflyer]

@daniel_duan this is exactly the joke that becomes a product requirement: mobile control is useful, but the phone screen should not pretend to be a full dev machine.

Faryo keeps the real session in tmux and gives phone/browser compact view + approve/interrupt. Snailflyer/faryo

[Summer @Snailflyer]

@whyaduck_ this Android stack is exactly the gap i keep seeing. Termux/SSH works, but reading a full terminal on a phone gets old fast.

Faryo keeps Codex CLI in tmux and puts a compact browser/phone layer above it. Snailflyer/faryo

[Summer @Snailflyer]

@_seemethere i think you are right about the end UI, but i don't want to throw away tmux as the durable substrate.

Faryo is basically: tmux owns the live agent sessions; web/mobile only gives a compact control layer. Snailflyer/faryo