Each repo has its own habits: cwd, shell history, tmux windows, env vars, local tools. Shelve lets iPhone reopen that SSH host workspace instead of recreating it, with no Shelve-specific package/daemon/relay/proxy required on the host.
@ShelveAppiOS This is a good framing. The less the agent path changes the actual dev environment, the fewer weird “works in agent, breaks locally” loops you get.
A Raspberry Pi is useful because it is already there. Shelve lets iPhone reach it over standard SSH for the host CLI, tmux, files, logs, services, and ports; no Shelve-specific package/daemon/relay/proxy required on the host.
Let the agent stay beside the repo. Shelve gives iPhone a standard SSH path to that host, so Codex, Claude Code, Gemini, or Aider run where your shell and env already live; no Shelve-specific package/daemon/relay/proxy required on the host.
@OpenAIDevs That phone handoff is the part worth making boring. Shelve keeps the work on your SSH host, then gives you tmux/files/logs/ports from iPhone when you need to check in.
@alexisbchz The terminal is only half the loop. The nice part is jumping from tmux to files/logs/ports on the same SSH host without needing a desktop session open.
@nessalazne I like keeping agents close to the real host. Shelve is built around that loop: run the CLI agent over SSH, then check tmux/files/logs/ports from iPhone.
@robinebers I like keeping agents close to the real host. Shelve is built around that loop: run the CLI agent over SSH, then check tmux/files/logs/ports from iPhone.
@robinebers I like keeping agents close to the real host. Shelve is built around that loop: run the CLI agent over SSH, then check tmux/files/logs/ports from iPhone.
Project context lives on the host: repo, shell history, tmux sessions, env, and local tools. Shelve lets iPhone reach that workspace over standard SSH, with no Shelve-specific package, daemon, relay, or proxy required on the host.
Shelve is built around the CLI host you already trust: connect from iPhone over standard SSH, use the same shell and tools, and keep moving without a Shelve-specific package, daemon, relay, or proxy on the host.
Phone workflows do not need to replace the host. Shelve lets your iPhone reopen the same machine over standard SSH, check tmux, logs, services, and ports, and make the next decision while the real work stays put.
A CLI agent can get stuck on the smallest prompt while you are away. Shelve lets you reopen the SSH host from iPhone, jump into tmux, check the files or logs around it, and give Codex, Claude Code, Gemini, or Aider the next nudge.
@agenticai_flow The terminal is only half the loop. The nice part is jumping from tmux to files/logs/ports on the same SSH host without needing a desktop session open.
The fastest mobile dev setup is the host you already use. Shelve makes it reachable from iPhone over standard SSH, with terminal, files, logs, services, system metrics, and ports close enough for quick checks.
The terminal is only half the loop. The nice part is jumping from tmux to files/logs/ports on the same SSH host without needing a desktop session open.
Raspberry Pi in the closet, server in a rack, VPS on the internet: if it speaks standard SSH, Shelve can make it usable from iPhone for terminal, tmux, files, logs, services, and ports.
tips for codex goals
sure you can use /goal but it also has a set_goal() function
its almost better to prompt the model to set its own goal, it will likely write a better prompt than you
@cmd_alt_ecs The terminal is only half the loop. The nice part is jumping from tmux to files/logs/ports on the same SSH host without needing a desktop session open.