04 / Local-first boundary
Use Pi remotely while your workspace stays on your computer
Pix moves the control surface, not your development environment. Pi reads your authorized workspace and runs tools on your Mac or Linux host; Pix provides the paired iPhone connection. Model requests still follow the provider you configure in Pi.
Two independent paths
Optional remote path
What does “local-first” mean in Pix?
Local-first describes Pix’s control boundary: Pi, your repository, tools, credentials, and native session files remain on the host computer. Pix Relay can forward encrypted transport frames, but it is not a hosted Pi runtime or workspace store.
| Boundary | Responsibility |
|---|---|
| Your Mac or Linux host | Runs Pi, reads the workspace, runs tools, and stores native sessions |
| Pix Relay (optional) | Routes authenticated encrypted frames without reading application payloads |
| Model provider you choose | Receives the model request that Pi sends under that provider’s policy |
What stays on your host?
- Your repository and authorized workspace roots.
- The Pi runtime and local development tools it invokes.
- Credentials used by Pi on that machine.
- Pi’s native JSONL session files and host-side runtime state.
What Pix Relay does not store
The relay forwards only authenticated encrypted frames. It does not decrypt, parse, queue, persist, or replay prompts, code, model output, or session payloads, and it never runs Pi.
| Pix Relay handles | Pix Relay does not handle |
|---|---|
| Channel-role authentication | Prompt or code inspection |
| Opaque encrypted-frame forwarding | Filesystem browsing |
| Connection and frame limits | Pi process execution |
| Endpoint routing | Session-payload storage |
For direct LAN versus relay behavior, see remote access to Pi Coding Agent.
Where do model requests go?
Pi may send relevant prompt context to the model provider you configure, such as a remote or local provider. That provider’s data handling is separate from Pix Relay. Pix does not promise that context sent to a selected model provider stays on your computer; check the provider policy for the session you choose.
Access is explicit
The host exposes only workspace roots you authorize and accepts only devices you pair. You can revoke a paired client without creating a Pix account or moving the workspace into a hosted service.
- Authorize canonical workspace roots on the host.
- Compare and approve each device pairing request.
- Revoke devices you no longer recognize or use.
Ready to use it? Start with the Pix installation guide.
Questions
Common questions
What does local-first mean for Pix?
Pi, your repository, tools, credentials, and native sessions stay on your authorized Mac or Linux host. Pix moves the remote control surface to your iPhone.
Does Pix upload my repository to Pix infrastructure?
No. Pix Host keeps the repository on the host, and Pix Relay forwards opaque encrypted frames instead of storing workspace or session payloads.
Can code or prompts leave my computer?
Pi may send relevant context to the model provider configured for the session. That model-provider path is separate from Pix Relay, which cannot read or store the encrypted Pix application payload.
Where do my credentials stay?
Credentials remain on the Mac or Linux host where Pi runs. Pix does not copy them to the iPhone or relay.
Does Pix require a cloud account?
No. Pix uses explicit device pairing and host workspace authorization instead of a hosted account system.
Which coding agent does Pix support?
Pix connects to Pi. It is a remote client for the Pi coding agent, not a general client for other coding agents.