klarluft/pitupitu

Worth a look if you already run coding agents on a machine you can leave on and want to nudge them from your phone without opening ports or a VPN. It is not a full remote IDE, and the cloud relay is a design choice you have to accept.

The problem

You leave Claude Code or Codex working in a terminal on your desktop or a remote box. Later, away from that machine, you want to know whether the agent finished, what it is blocked on, or to send one more instruction. Today that usually means SSH from a phone, reattaching to a terminal, or keeping a chat session open on the right machine. With pitupitu, you talk to pitupitu.chat from a phone browser and the request is forwarded to the box agent, through herdr, into a pane running your own agent. The result you get back is the agent's screen, so you can start, check on and unblock sessions without being at the desk — the project describes exactly this start/check/unblock loop.

What's different

The mechanism is an outbound-only link: the box agent dials wss://api.pitupitu.chat/v1/box and nothing listens on your machine, so no open port, VPN or certificate is needed. The cloud can only request a fixed set of operations (list/open/close workspaces and tabs, start an agent in a pane, send a prompt or keys, read and wait on its screen, update pitupitu or herdr), with no shell and no arbitrary command. Your unmodified claude and codex run under your own logins and permission mode, and pitupitu never reads or uses their credentials.

The practical benefit is a narrow, enumerable surface rather than a general remote terminal. The trade-off is equally clear: the hosted cloud is in the path between your phone and your agents, and a fixed operation list means anything outside it is not reachable — you cannot run an arbitrary command from the phone. The README does not spell out failure behavior when the outbound link drops.

Who should try it

A good fit is someone who keeps a workstation or home server running agents and wants a quick phone check-in — "what is left on this project?" — without setting up remote access themselves. It also suits people who prefer speaking to typing a prompt on a small screen. A poor fit is someone who wants a complete remote development environment, needs to run arbitrary shell commands remotely, or is unwilling to route session metadata through a hosted service; those users should look elsewhere rather than treat this as an SSH replacement.

Requirements and limitations

You need macOS or Linux as the box (binaries target Linux x86_64/arm64 and macOS Intel/Apple silicon), with claude and/or codex — or another agent herdr recognizes — installed and signed in; pitupitu installs herdr if it is missing and does not touch agent logins. An account is required, with a sign-in code approved at pitupitu.chat, and one account can hold many named boxes. Windows is not listed as a supported box platform.

Upkeep matters. pitupitu never updates itself or herdr, so checking pitupitu status and running pitupitu update (or update all) is a recurring duty. History reading is on by default: session logs from the last 7 days (newest 300) plus git activity in the relevant repositories are read and sent, so review the privacy page if that scope is unacceptable. Audio is claimed not to be stored, and logs carry metadata only, per the README.

HotRepo's take

HotRepo has no comparable daily-board history for this 10-day-old repository; the only recorded signal is a NEW-REPOSITORY board (新项目榜, rust) observation on 2026-10-27 at #22 with 212 total stars, which is a snapshot, not a growth measurement. Persistence cannot be judged from that. Before adopting, read the exact operation list in the box-link documentation and decide whether you accept the hosted relay in that path.

Project source and documentation