<div align="center"> <img src="docs/image/readme/logo.png" alt="PI-Desktop" width="108" />

PI-Desktop

A modular desktop workspace for AI agents

Bring projects, agents, models, plugins, and workflows into one persistent desktop environment.

Local-first · Model-agnostic · Plugin-powered · macOS / Windows / Linux

<br />

<br />

Download · Documentation · Build a Plugin · Screenshots · 简体中文

<br /> <img src="docs/image/readme/home.webp" alt="PI-Desktop" width="94%" /> <br />

Your projects stay local · Your models stay replaceable · Your workspace stays yours

</div>

Current release line: 0.15.x (Early Preview).

---

Why PI-Desktop?

Terminal agents are great at execution. IDE agents are great at living inside an editor.

PI-Desktop goes one step further:

Give AI agents a persistent, independent, and extensible desktop workspace of their own.

<table> <tr> <td width="25%" valign="top">

Independent Workspace

No dependency on a specific IDE or terminal.

Projects, sessions, reviews, previews, and agents all live in their own workspace.

</td> <td width="25%" valign="top">

Plugin-Powered

Plugins extend more than the agent.

Add panels, views, widgets, tools, MCP servers, themes, and background services.

</td> <td width="25%" valign="top">

Agent Orchestration

One agent is not always enough.

Delegate to Subagents or coordinate full Worker Sessions in parallel.

</td> <td width="25%" valign="top">

Model Freedom

Cloud models, local models, custom gateways, compatible APIs.

Switch models without rebuilding your workflow.

</td> </tr> </table> <div align="center">

It is not a wrapper around one model. It is not another IDE extension.

It is a desktop platform for agent workflows.

</div>

---

Plugins are part of the workspace, not an afterthought

PI-Desktop keeps the Core focused.

Your actual workflow is assembled through extensions.

<table> <tr> <td width="33%" valign="top">

Agent

Extend what the agent can do

Agent Tools Skills Completion pi Extensions

</td> <td width="33%" valign="top">

Workspace

Extend the desktop itself

Commands Panels Work Panel Views Floating Widgets Themes

</td> <td width="33%" valign="top">

Platform

Extend the runtime

MCP Servers Resident Services Plugin Message Bus

</td> </tr> </table>

A plugin does not have to be “just another tool.”

It can be an entire product:

Voice Agent
├── Floating Widget
├── Speech Service
├── Agent Tool
└── Commands

GitHub Workspace
├── Work Panel
├── MCP Server
├── Agent Tools
└── Background Service

Session Analytics
├── Dashboard
├── Commands
└── Workspace View

What can a plugin add?

| Capability | What it enables | | ------------------- | -------------------------------------------------------------- | | Command | Add actions to the global command system | | Panel | Open a standalone plugin interface | | Floating Widget | Build voice orbs, status lights, timers, and other floating UI | | Work Panel View | Add new views to the right-side workspace | | Agent Tool | Register tools callable by the agent | | Completion | Use the models already configured by the user | | Skill | Add reusable agent capabilities and workflows | | Theme | Customize workspace appearance | | MCP Server | Connect local or remote MCP servers | | Service | Run persistent background work | | Message Bus | Let plugins communicate with each other |

Plugins can be distributed as .piplug packages or installed through the marketplace.

<div align="center">

Build your first plugin →

</div>

---

One foundation, many workflows

                         PI-Desktop
                             │
          ┌──────────────────┼──────────────────┐
          │                  │                  │
        Agent            Workspace           Platform
          │                  │                  │
     Agent Tools           Panels              MCP
       Skills             Widgets            Services
     Subagents             Views            Message Bus
   pi Extensions          Themes
          │                  │                  │
          └──────────────────┼──────────────────┘
                             │
                       Your Workflow

PI-Desktop can simply be your coding agent.

Or you can turn it into:

AI Development Workspace · Voice Agent · DevOps Console · GitHub Workspace · Data Assistant · Multi-Agent Control Center · Automation Platform

The Core provides the foundation. Plugins decide what your workspace becomes.

---

Three ways to work

<table> <tr> <td width="33%" valign="top">

Agent

Give it a task. Let it work.

Read code, edit files, run commands, test, and iterate.

Best for day-to-day development.

</td> <td width="33%" valign="top">

Plan

Review the approach before execution.

The agent studies the project first and produces an implementation plan.

Best for refactors and high-risk changes.

</td> <td width="33%" valign="top">

Goal

Define the outcome. Let the agent choose the path.

Lock the objective and acceptance criteria, then let the agent drive execution.

Best for complex and long-running tasks.

</td> </tr> </table>

Privileged operations still pass through PI-Desktop's permission layer.

---

When one agent is not enough

Complex work should not be forced into one context window.

PI-Desktop provides two levels of delegation.

Subagents

Delegate independent work to background agents:

Code exploration · Implementation · Test analysis · Research · Review

Each Subagent gets its own context and reports the result back to the parent agent.

Session Orchestrator

For longer-lived work, delegate to full Worker Sessions.

Main Session
│
├── Worker A
│   └── Frontend
│
├── Worker B
│   └── Backend
│
├── Worker C
│   └── Tests
│
└── Worker D
    └── Review

Workers are full PI-Desktop sessions:

Independent context · Independent execution · Directly inspectable · Reusable · Full transcript

<table> <tr> <td width="50%"> <img src="docs/image/readme/session-orchestrator-overview.png" alt="Session Orchestrator" /> <p align="center">_{Coordinate multiple Worker Sessions from one parent Session}</p> </td> <td width="50%"> <img src="docs/image/readme/session-orchestrator-worker.png" alt="Worker Session" /> <p align="center">_{Each Worker remains a full, inspectable Session}</p> </td> </tr> </table> <div align="center">

Move from “one agent helps me code” to “multiple agents divide and complete the work.”

</div>

---

Built for work that lasts

PI-Desktop is organized around:

<div align="center">

Project → Session → Agent → Work

</div>

—not around disposable chat threads.

You can:

• Manage multiple projects and sessions
• Pin, archive, branch, and search sessions
• Queue prompts while an agent is already running
• Reference project files with @
• Use slash commands
• Review diffs
• Inspect command output
• Work with the right-side Work Panel
• Keep streaming checkpoints
• Recover interrupted work whenever possible

A Session can continue across multiple app launches.

---

See what the agent is doing

<table> <tr> <td width="50%"> <img src="docs/image/readme/chat_en.png" alt="PI-Desktop Session" /> <p align="center">_{Persistent Sessions instead of disposable chats}</p> </td> <td width="50%"> <img src="docs/image/readme/model_en.png" alt="PI-Desktop Model" /> <p align="center">_{Switch models and reasoning levels inside the Session}</p> </td> </tr> <tr> <td width="50%"> <img src="docs/image/readme/plugins_en.png" alt="PI-Desktop Plugins" /> <p align="center">_{A plugin marketplace that extends both the agent and the desktop}</p> </td> <td width="50%"> <img src="docs/image/readme/addmodel_en.png" alt="PI-Desktop Providers" /> <p align="center">_{Connect your own provider, gateway, or local model}</p> </td> </tr> </table> <div align="center">

Explore more screenshots →

</div>

---

Swap the model, keep the workflow

PI-Desktop does not tie your workflow to a single model vendor.

Use:

OpenAI · Anthropic · OpenAI-Compatible APIs · Custom Gateways · Ollama · LM Studio · Local Models

Configure each model independently:

Provider · Model ID · Context Window · Output Limit · Reasoning / Thinking · Temperature · OAuth · API Key · Endpoint

Different Sessions can use different models.

The same Session can switch models at any time.

Planning     → Model A
Coding       → Model B
Review       → Model C
Private Task → Local Model

The model is a replaceable component of the workflow — not the workflow itself.

---

Already using another coding agent?

Keep your existing work.

PI-Desktop can import local sessions from:

Claude Code · Codex · OpenCode · Pi

---

Local-first

PI-Desktop does not require you to move your development environment into our cloud.

| Data | Default behavior | | -------------------- | ----------------------------------------- | | Projects | Local | | Sessions | Local | | Settings | Local | | Logs | Local | | API credentials | OS Keychain | | PI-Desktop telemetry | None | | Model requests | Sent directly to your configured provider |

No mandatory PI-Desktop account.

No mandatory PI-Desktop relay.

When using a remote model, the context required for the request is sent directly to that provider.

---

You control the permissions

Agents can read files, edit code, run commands, call tools, use extensions, and delegate work.

Privileged operations still pass through the permission layer:

Agent
  ↓
Tool Request
  ↓
Permission Layer
  ↓
Allow / Ask / Deny
  ↓
Execution

You decide how much autonomy each Session gets.

---

Get started

<table> <tr> <td width="25%" valign="top">

01

Download

Install PI-Desktop

</td> <td width="25%" valign="top">

02

Connect a model

Configure a Provider

</td> <td width="25%" valign="top">

03

Open a project

Choose a local repository

</td> <td width="25%" valign="top">

04

Start working

Agent / P