Pi stays local
Pix launches and supervises the Pi you already use. Your files and native JSONL sessions remain on the host.
Pix runs next to Pi on your machine, then gives paired devices a direct or encrypted way to pick up the same sessions.
you Check the relay boundary against the v1 schema.
Reading protocol/schema/v1.md
pi Relay forwards opaque frames. It does not parse application payloads.
you
Pix launches and supervises the Pi you already use. Your files and native JSONL sessions remain on the host.
Nearby devices use Bonjour discovery and a direct TCP path whenever the network allows it.
The same Pix wire frames travel over the remote path, with the relay forwarding ciphertext only.
Only canonical workspace roots you authorize are exposed to a paired client.
A client gets access after an explicit approval step on the host, and can be revoked later.
Host, CLI, protocol fixtures, relay, and the public macOS client are available to inspect.
brew tap ZainCheung/pix https://github.com/ZainCheung/pix.git
brew install --cask ZainCheung/pix/pixcurl -fsSL https://pix.deepoke.com/install.sh | shOn the machine where you run the Pix Host. Pix does not move your workspace into a hosted environment or create a second session store.
The client discovers the host over Bonjour and prefers a direct TCP connection. The encrypted Pix wire protocol is the same on that path.
No. The relay forwards authenticated opaque encrypted frames and does not decrypt, parse, queue, or persist application payloads.
On Linux it downloads the matching release archive and installs the pix CLI into ~/.local/bin. On Apple Silicon it also installs Pix.app into ~/Applications.
No. Pix uses explicit workspace authorization and device pairing instead of a hosted account layer.