Remote-first development

Your laptop is a window, not the workstation.

Pi Web is built around a simple shift: development should live where the work happens, not where your current keyboard happens to be.

Local-only development can become the blocker

Local development made sense when one human drove every keystroke from one machine. With AI agents, the work can outlive the laptop session. Agents need stable repositories, shells, tools, secrets, build caches, and time to keep running.

When all of that is tied to a laptop, the laptop becomes the bottleneck: close the lid, change devices, lose network, reboot, or run out of battery, and the work environment is interrupted.

Remote AI-driven development unlocks persistent work

Run the environment on a machine that stays on: a dev box, home server, cloud VM, workstation, or private network host. Keep agents and worktrees there. Connect from whatever screen you have.

↻

Always available

Sessions keep existing after browser disconnects and can be resumed later.

▦

Parallel by default

Use worktrees and persistent sessions to let multiple agent streams progress independently.

⌁

One real environment

Dependencies, caches, credentials, and repository state stay where the agents run.

The browser becomes the control plane

Your device should not have to be the editor, terminal, build server, and agent runtime. In Pi Web, the browser is the cockpit: supervise sessions, redirect agents, inspect transcripts, and review progress while the development environment stays remote and stable.

Laptop, phone, tablet, desktop: they are just windows into the same running work.

The human role becomes direction, judgment, and review

Remote-first does not remove the human. It moves the human away from carrying the whole development environment and toward higher-leverage work: choosing direction, setting constraints, reviewing changes, and deciding what ships.