Native workspace for pi

Stay focused on the session, not the terminal plumbing.

Pi Client brings session browsing, prompts, live output, and run control into an early native macOS workspace.

  • macOS 11+
  • Universal app
  • Version 0.0.2

Universal ZIP for Apple silicon and Intel Macs

Pi Client window showing synthetic sessions and a sanitized coding-agent conversation.

A real Flutter render with synthetic project paths, sessions, prompts, and agent output.

Current capabilities

The essential session loop in one window.

The preview focuses on the actions already supported by the current macOS MVP.

Browse sessions

Refresh session summaries, open a conversation, and read visible message history.

Create and continue work

Create a session for an absolute project path and send the next prompt.

Follow live output

Watch assistant updates arrive through the selected session event stream.

Stop an active run

Interrupt the current agent run without leaving the desktop workspace.

How it works today

A native client over a transitional compatibility bridge.

The current preview uses pi-web 0.8.11 for session and runtime access. Pi Client does not read pi session files directly.

Pi-web compatibility is an early bridge, not Pi Client’s long-term product identity. A future versioned, Pi SDK-based transport remains planned; this release does not include WebAssembly support.

Get started

Run the preview with your existing pi setup.

You need macOS 11 or newer, pi-web 0.8.11, and a working pi model-provider configuration.

  1. 01

    Start pi-web

    Run npx @agegr/pi-web@0.8.11 --no-open and keep it available.

  2. 02

    Download Pi Client

    Download the Universal ZIP, extract Pi Client.app, and review the unsigned-preview warning.

  3. 03

    Connect and work

    Open the app, enter the pi-web URL and optional password, then select Connect.

Read the complete setup guide

Security boundary

Keep the agent endpoint private.

Pi-web can expose an agent with the host process’s project and tool permissions. Treat the endpoint as privileged infrastructure.

  • Keep pi-web on loopback unless remote access is intentional.
  • For remote access, use HTTPS through a trusted reverse proxy or a VPN.
  • Use a strong PI_WEB_PASSWORD, but do not rely on Basic Authentication to encrypt traffic.
  • Pi Client keeps the password in memory and excludes it from workspace state, URLs, and payload logs.

Preview limitations

  • macOS only; no browser or WebAssembly client is included.
  • Unsigned and unnotarized; Gatekeeper warnings are expected.
  • Compatible with observed pi-web 0.8.11 behavior, which is not a declared stable API.
  • No model, provider, skill, plugin, file, Git, or worktree management.
  • No session rename, deletion, export, branching, rich Markdown, or media rendering.

Try the macOS preview or follow the project in public.

Pi Client is open source and early. Use GitHub Issues for bugs, compatibility reports, and feature requests.