Remote For Xirp
See and steer your coding agents from your phone.
A mobile web app for the Xirp desktop app's agent daemon. The sessions running on your Mac — Claude Code, Codex, Gemini, or whatever else Xirp is driving — can be watched and answered from an iPhone or Android without going back to the desk. It runs on your own network, not through anyone's cloud.
Install
curl -fsSL https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/install.sh | sh
That drops a universal binary into ~/.local/bin and stops. Nothing starts
listening because you piped a script into a shell — starting it is one explicit
command, which prints a QR code to scan with your phone:
xirp-remote interfaces # which address can a phone reach?
xirp-remote install --generate-key # start it, and print a QR codeWhat it does
Machines, then projects, then sessions
Several machines running Xirp, each with its projects and their sessions.
Chat, transcript, or the real tmux pane
The pane is the actual one, so slash commands, model pickers and permission prompts work without this app knowing they exist.
Review the diff
What a session changed, uncommitted and against its base branch, with the file diff and a link to the branch's pull request.
Notifications
Web Push when an agent finishes, fails, or wants an answer — with the app closed.
Start, fork, hand over
Start a session with a project, agent and model. Fork one that went the wrong way, or hand it to a different agent.
Pair by QR
The access key travels in the URL fragment, so it never reaches a server log, and the page clears it from the address bar.
What you need
- macOS, and not incidentally — the daemon's token exists only in the Xirp app's process environment, which only the same user can read.
- Xirp installed and running. When the app is quit there is nothing to control.
- A phone on the same network, or reaching the Mac over a VPN.
- Nothing else. One Go binary, no Node, no database.
What it deliberately will not do
It reaches 33 of the daemon's 212 message types. No git writes, no terminal attach, no session deletion, no settings changes. Remote approval of permission prompts is absent because the daemon holds a request open for about half a second before falling through to the agent's own dialog — no polling client can catch that, and pretending otherwise would be worse than leaving it out.