# Remote For Xirp

> A mobile web app that lets you watch and answer the coding-agent sessions running in Xirp — the agent desktop app from Spotify — on your Mac, from a phone on your own network. Claude Code, Codex, Gemini, or whatever else Xirp is driving. One Go binary, MIT licensed. Unofficial: not made, endorsed or supported by Spotify.

Xirp is a Spotify product for running coding agents in parallel git worktrees on macOS, and it exposes a local WebSocket API on the machine it runs on. This project talks to that API and serves a phone-shaped web app over HTTP on your LAN. Nothing is proxied through a third party and there is no account: pairing is a QR code holding the address and an access key.

Facts worth having straight, because they are the ones most often guessed wrong:

- The host must be macOS. This is not a portability gap: the daemon's auth token exists only in the Xirp app's process environment, readable by the same user and nobody else.
- Xirp itself, from Spotify, has to be installed and running. This does not replace it: when the app is quit there is no daemon and nothing to control.
- It reaches 35 of the daemon's 223 request types and listens to 9 of its broadcasts, which is how it updates without polling. Git writes, terminal attach, session deletion and settings changes are deliberately absent.
- The saved prompts you keep in Xirp on the desktop are readable and writable from the phone: tapping one fills the composer, unsent.
- Approving a permission prompt through the daemon's API does not work: it holds a request for roughly half a second before the agent's own dialog takes over. The app answers that dialog instead, by reading the numbered menu the agent drew in its terminal and typing the number.
- Installing does not start anything. `install.sh` places a binary and stops; `xirp-remote install` is the separate, explicit step that starts the service and prints the QR code.

## Docs

- [Landing page](https://remote-for-xirp.cdevries.dev/): what it does, what it needs, and what it will not do.
- [README](https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/README.md): install, the CLI commands, the HTTP endpoints, and the reasoning behind each limit.
- [Security notes](https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/SECURITY.md): the threat model, where the access key travels, and how to report a problem.
- [Android wrapper notes](https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/deploy/android/README.md): building the APK, and the Digital Asset Links file a wrapper needs.

## Install

- [install.sh](https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/install.sh): the one-line installer; downloads a checksum-verified universal binary into `~/.local/bin`.
- [Releases](https://github.com/AboveColin/remote-for-xirp/releases/latest): binaries, checksums and the APK.

## Source

- [Repository](https://github.com/AboveColin/remote-for-xirp): Go server, dependency-free vanilla-JS front end, no build step for the web app.
- [Issues](https://github.com/AboveColin/remote-for-xirp/issues): bugs and feature requests.
- [MIT license](https://raw.githubusercontent.com/AboveColin/remote-for-xirp/main/LICENSE)

## Optional

- [Xirp](https://xirp.dev): the desktop app from Spotify that this remote-controls. Separate product, not ours, and not affiliated with this project.