PiChamber

Roadmap

What’s shipped. What’s coming.

PiChamber began as a community fork of OpenChamber, rebuilt around the Pi SDK. Desktop, server, mobile, and native pull request and issue workflows have shipped. Plugins are what is next. The goal is a small core that grows through plugins, not bloat.

13 shipped · 0 in progress · 3 planned

  1. Integrations CatalogPlanned

    Browse and install Pi skills, extensions, and MCP servers from one place instead of wiring config files by hand.

  2. Native PluginsPlanned

    First-party plugins that double as examples of how PiChamber plugins work: MCP, subagents, todo, and questions. These are normal Pi extensions with additional pichamber.ui support. That UI layer is what makes them PiChamber plugins.

  3. PiChamber Plugin EcosystemPlanned

    The main plugin system for PiChamber: extend the workspace beyond the core app, including additions to the UI such as panels, cards, and views shipped as plugins.

  4. Extension RenderingShipped

    Pi extensions render cards, live panels, forms, and sandboxed app views inside the workspace. Learn more →

  5. Native PR and Issues IntegrationShipped

    Pull requests and issues are first-class in the workspace, on top of the Git and GitHub integration.

  6. CLI + Update ChannelsShipped

    Guided pichamber serve and update flows, logs, tunnels, and connect URLs. Desktop and server updates follow Stable or Release Candidate channels with release notes.

  7. Git & GitHub IntegrationShipped

    Full Git sidebar with unified header, history and graph views, PR creation, and sessions started from issues.

  8. Terminal + FilesShipped

    xterm.js terminal with clipboard policy and tab dropdown, revision-guarded file saves, file search, and background worktree task creation.

  9. Skills, Prompts & Project TrustShipped

    Existing Pi extensions keep their tools, commands, hooks, and UI prompts. Skills, prompt templates, AGENTS.md, and project trust apply when sessions go idle.

  10. 40+ Providers + Custom ModelsShipped

    Configure Pi providers and add custom models manually. Credentials never leave the host.

  11. Session WorkspaceShipped

    Create, resume, fork, archive, and delete Pi sessions. Steer or abort live work while reasoning, tools, and token usage stream in real time.

  12. Multi-Device PairingShipped

    Pair desktop, browser, and mobile to one PiChamber server over the authenticated API with one-time pairing links. Revoking a device ends live access immediately. Learn more →

  13. Browser + PWAShipped

    Self-hosted server with web UI and installable PWA. Run with pichamber serve, npm, or Docker on a host you control. Learn more →

  14. Mobile AppShipped

    Native mobile clients paired to a PiChamber server over the authenticated API. Run Pi sessions from your phone with live chat, attachments, and reconnect handling. Learn more →

  15. Desktop AppShipped

    macOS (unsigned), Windows, and Linux apps. Linux ships as .deb, .rpm, and portable AppImage with safe updates and rollback. Signed macOS builds are not planned for now. Learn more →

  16. Pi-Native Session DaemonShipped

    Fork rewritten around the Pi SDK: Pi owns sessions, providers, prompts, and skills while PiChamber owns the workspace, auth, and device connections.

Something missing? Open an issue or start a discussion — the roadmap follows what the community actually needs.

Try PiChamber now.

Download PiChamber

Questions? Join our Discord →