How PiChamber works.

PiChamber is an open-source workspace for Pi Coding Agent. A PiChamber server runs a private Pi session daemon on your machine, exposes a web UI and APIs, and lets trusted devices work with the same Pi sessions — desktop app, browser, or phone.

PiChamber uses the Pi SDK directly. You do not need a separate Pi CLI install or an independently managed Pi server — the PiChamber server creates and owns the daemon for you.

• Create, resume, fork, archive, and delete Pi sessions
• Steer or abort live agent work and watch reasoning and tool streams
• Configure providers, extensions, skills, and prompts on the host
• Pair multiple clients to one or many servers you control

PiChamber is one workspace model across every client. You run a PiChamber server on a machine you control, then reach it from a browser, desktop app, or phone — same sessions, same host filesystem, same credentials on the server.

• Browser — open your server URL in Chrome, Safari, Firefox, or any modern browser for the full PiChamber web UI
• Desktop app — native PiChamber for macOS, Windows, and Linux; install once, add your servers, and work without keeping a browser tab open
• Mobile app — PiChamber on Android (and iOS where available) to pair with servers, check sessions, and steer agent work from your phone

Every client is a remote view into the server you connected to. Execution, API keys, skills, and project files stay on that host — the app or browser streams the UI to you.

This website (PiChamber Web) is separate from those clients: it is the landing page for downloads, overview, and guides like this one. The open-source app and server package live in the main PiChamber repository.

Install the global server package with Node.js 22+ or Bun. Use whichever package manager you already have.

When a new release ships, update in place without reinstalling through your package manager:

One command starts the web UI and a private Pi session daemon on the host:

On a VPS or always-on machine, enable a startup service so PiChamber survives reboots. This creates a native service (systemd on Linux, launchd on macOS) that starts PiChamber when the machine boots.

Desktop, browser, and mobile all connect to the same Pi workspace on your server. Pick whichever pairing flow is easiest.

• Scan a QR code — open the server in your browser and scan the pairing QR from PiChamber on your phone or desktop
• Add server manually — in any PiChamber client, choose Add server and enter your PiChamber URL and password

Pairing grants a device access to the server workspace. Revoke access from the server when a device is no longer trusted. Remote clients operate on the server filesystem and use the server’s Pi configuration — not a copy on the client.

Run a PiChamber server on your desktop, in WSL, on a VPS — wherever you need Pi. Add each server to PiChamber on your phone, laptop, or browser and switch between them from a single client.

• Your main computer for everyday work
• WSL or a local VM for Linux-native projects
• A cloud VPS for always-on agent sessions

Pair once per server. Your API keys, skills, and project files stay on each host — clients never receive stored provider credentials.

Desktop and mobile builds are distributed from GitHub releases. Install the app for your platform, then add a server by QR code or URL — the same pairing flow as the browser UI.

PiChamber is not a sealed GUI. It follows Pi’s philosophy — minimal, fast, and hackable. Your providers, extensions, skills, and prompts stay yours.

• 40+ built-in providers plus custom endpoints via models.json or extensions
• API keys and OAuth credentials are stored on the server host
• Extensions that work with Pi work in PiChamber — same daemon and session model
• Switch models mid-session from the workspace UI

A PiChamber server is a single-owner workspace. Anyone you pair or authenticate can act on its sessions and server filesystem — treat pairing like handing someone access to that machine.

• Use a strong UI password when the server is reachable beyond localhost
• Do not share pairing links or connection tokens
• PiChamber never returns stored provider credentials to browser or mobile clients
• Revoke devices you no longer trust from the server settings

• Do I need to install Pi separately? No — PiChamber owns the Pi session daemon on the server host.
• Where do my files live? On the server you connected to. Remote clients stream the UI; execution stays on the host.
• Can I use my existing Pi extensions? Yes — same Pi daemon, extensions, skills, and hooks.
• Is PiChamber open source? Yes — MIT licensed, community fork evolved from OpenChamber for Pi.
• What if something breaks? Check server logs, confirm the server is reachable, and see troubleshooting in the main docs.

This page is an overview for newcomers. Command flags, advanced configuration, and edge cases live in the PiChamber repository docs.