Multi-Agent Council Planning

Pi, Claude, and Codex each produce an initial plan, share and converge, and Pi presents the agreed consensus plan before anything is built. All members plan read-only; Pi is the only agent that edits files.

This is off by default. Enable it in Settings → "Multi-Agent Council Planning". A confirmation dialog warns that it increases token/credit usage, because each request runs multiple agents.

Members. Pi, Claude, and Codex. The app auto-detects each CLI cross-platform; only detected agents can be enabled, via per-agent checkboxes. At least two members must be available, or a run is refused. Pi always merges the plans into the final consensus, even when not checked as a planner.

Read-only planning. Every member plans read-only (Claude --permission-mode plan, Codex --sandbox read-only, Pi with write tools excluded) — they produce plans but never modify files. Only Pi implements the approved result.

Live output. Each member streams its plan live in its own card during the consulting phase, with an elapsed timer.

Consensus modes:

• One debate round (default) — each member sees the others' plans and revises once, then Pi merges. You watch them converge.
• Arbiter merge — faster/cheaper. Pi synthesizes the initial plans directly with no debate round.

Per-member timeout (10–600s, default 240s) bounds each member. A member that times out or errors is dropped, and the run proceeds as long as at least one plan was produced.

To use it: with the feature enabled, type your request and click Plan with Council in the composer. Review each member's plan and Pi's merged consensus plan. If you want changes, type feedback in Request changes to the plan… and Pi revises the consensus (repeat as needed). When you're happy, click Implement this to have Pi build it. The panel collapses once a plan is ready so the output stays readable.

Getting started

You need Pi installed first:

npm install -g @earendil-works/pi-coding-agent

On Linux, grab the AppImage from Releases:

chmod +x Pi-Desktop-linux-x64.AppImage
./Pi-Desktop-linux-x64.AppImage

macOS

Download the .dmg (Apple Silicon / arm64) from Releases, open it, and drag Pi Desktop to Applications.

Builds are not yet signed or notarized. Because the download is unsigned, macOS quarantines it and, on first launch, reports "Pi Desktop is damaged and can't be opened. You should move it to the Trash." The app is not actually damaged — this is Gatekeeper blocking an unsigned app. macOS does not offer an "Open Anyway" button for this message, so clear the quarantine flag in Terminal:

xattr -dr com.apple.quarantine "/Applications/Pi Desktop.app"

Then open the app normally. You only need to do this once.

If macOS instead says the app "cannot be opened because Apple cannot check it for malicious software," you can allow it without Terminal: open System Settings → Privacy & Security, scroll to the Security section, and click Open Anyway next to the Pi Desktop notice, then confirm with Touch ID / your password.

Prefer to skip the unsigned-app warnings entirely? Build from source. A build you compile yourself runs locally without Gatekeeper blocking it, so there's no signing/notarization prompt and no quarantine flag to clear. See Build it yourself → Linux / macOS below.

Windows

Download from Releases: the installer (…-win-x64-setup.exe, recommended) or the portable …-win-x64.exe. Builds are unsigned, so SmartScreen may warn — choose More info → Run anyway. If file edits or saves fail, see the Controlled Folder Access note below. Windows is community-tested; please open a bug report if you hit an issue.

Keyboard shortcuts

Build it yourself

Linux / macOS

git clone https://github.com/FaqFirebase/pi-desktop.git
cd pi-desktop
npm install
npm run dev

Windows

Windows requires extra steps because node-pty (the terminal backend) compiles a native module against Electron's ABI.

1. Install prerequisites

Install all of the following before cloning:

• Git for Windows
• Node.js LTS — use the official Windows installer (adds node and npm to PATH)
• Visual Studio Build Tools 2022 — download from Visual Studio downloads
  • Select the Desktop development with C++ workload
  • Open Individual components, search Spectre, and install Spectre-mitigated libs for v143 toolset

⚠️ Use VS Build Tools 2022, not 2026. node-pty requires Spectre-mitigated runtime libraries. VS 2022 stable (v143 toolset) ships them. VS 2026 preview (v180 toolset) does not — npm install will fail with MSB8040: Spectre-mitigated libraries are required for this project.

2. Add a Windows Defender exclusion (recommended)

Defender can block or slow npm install on projects with many small files. Before cloning, add an exclusion:

Settings → Privacy & Security → Windows Security → Virus & threat protection → Manage settings → Exclusions → Add a folder → (pick where you'll clone the repo)

3. Clone and install

git clone https://github.com/FaqFirebase/pi-desktop.git
cd pi-desktop
npm install

The postinstall script rebuilds node-pty against Electron's ABI and downloads the Electron binary. First install may take a few minutes.

If the Electron binary is missing after install, use the manual Electron binary download steps below. This is the confirmed fallback on Windows when Electron's postinstall extraction leaves a partial dist folder.

4. Install Pi

powershell -c "irm https://pi.dev/install.ps1 | iex"

Open a new terminal after this so the updated PATH takes effect.

5. Run

npm run dev

Common Windows errors

Controlled Folder Access (Ransomware protection)

Windows Controlled Folder Access protects Documents, Desktop, Pictures, and similar folders, silently blocking apps it doesn't trust from writing to them. Because Pi Desktop is a coding agent that edits files, this shows up as intermittent EPERM/EACCES failures — during npm install, when the agent edits code, or when you save a file — if your repo or projects live inside a protected folder.

The reliable fix is to keep code out of protected folders. Clone the repo and put your projects somewhere unprotected, for example:

# Not C:\Users\<you>\Documents\... — use an unprotected path:
git clone https://github.com/FaqFirebase/pi-desktop.git C:\dev\pi-desktop

If you must keep code under Documents/Desktop, allow the app instead:

Windows Security → Virus & threat protection → Ransomware protection → Manage ransomware protection → Allow an app through Controlled folder access → Add an allowed app — add the installed Pi Desktop.exe (and, for development, node.exe, git.exe, and electron.exe).

The portable .exe re-extracts to a temporary folder on each launch, so allow-listing it doesn't stick. Prefer the installer (Pi-Desktop-<version>-win-x64-setup.exe) if you rely on the allow-list approach.

Manual Electron binary download

If npm install completes but the app won't launch because Electron is missing or corrupted, download it directly from GitHub and unpack it into place. This is the known-good fallback when node_modules\electron\dist contains only partial contents, such as locales, and no electron.exe.

Replace 39.8.10 with the version in node_modules/electron/package.json if it differs.

$ver = "43.0.0"
$url = "https://github.com/electron/electron/releases/download/v$ver/electron-v$ver-win32-x64.zip"
$zip = "$env:TEMP\electron-v$ver-win32-x64.zip"
Invoke-WebRequest -Uri $url -OutFile $zip
if (Test-Path node_modules\electron\dist) { Remove-Item -Recurse -Force node_modules\electron\dist }
Expand-Archive -Path $zip -DestinationPath node_modules\electron\dist -Force
"el