Build faster. Think bigger.

A native desktop
workspace for Pi.

Pipkin brings the Pi coding agent into a focused Rust/GPUI desktop client. Stream answers, follow tool calls, and inspect file changes beside the conversation.

View source Getting started

Alpha on Arch / Omarchy Wayland · No published release yet

Small prompts.
Bigger momentum.

PipkinFor developers
who move quickly.

Pipkin, a hooded robot mascot, working on a laptop

Pipkin's dark desktop interface: a simulated agent conversation, tool activity and a changes pane with file diffs — Demo · simulated agent

Scroll to inspect the full desktop screenshot

Converse

Stream replies and steer, queue, or stop an active run.

Inspect

Expand tool output and review diffs beside the conversation.

Continue

Return to saved drafts, conversations, and search.

The work, in view.

Readable tool cards, file changes, and both dark and light themes. These are screenshots of Pipkin’s built-in simulated demo, not a recording of a real model run.

Demo conversation showing expandable tool cards beside a response — Tool activity at a glance · simulated demo

Demo changes pane showing a file diff and list of changed files — Diffs and files changed · simulated demo

Pipkin's light theme showing a simulated conversation and changes pane — Light theme · simulated demo

Pi is the agent.
Pipkin is the desktop workspace.

Pi runs the agent and owns its sessions. Pipkin is the native client: it shows streaming answers, tool activity, and diffs, while keeping drafts and saved copies on your machine.

Built workflows; broader native qualification is still in progress.

Opena project
Startor resume
Followthe agent
Inspectchanges
Steeror stop

Built in public.
Qualified carefully.

Pipkin runs with a real Pi engine and has a buildable package. It is alpha software: installation on a clean machine, accessibility, scaling, and broader platforms need more checks. Read the full status.

Reviewed October 5, 2026 · Source revision eaab8ef

Area	Current status
Real-engine workflow	Execution, steering, queueing, and recovery are built and tested against a real engine; real-model use is reported on the author's machine.
Local product	History, search, tool output, extension dialogs, and offline saved copies are built. Native accessibility and scaling gates are only partly run.
Install and package	Bundled-engine package and diagnostics are built and scratch-prefix checked. Clean-machine install is unverified; no release is published.
Platforms	Arch / Omarchy Wayland: alpha. X11 starts under Xwayland only; other Linux environments are unverified. macOS and Windows are not supported.

Good questions.
Straight answers.

What works now, and what still needs to be checked?

Is Pipkin a new agent?

No. Pi is the coding agent. Pipkin is a native desktop client for Pi’s conversations, tool activity, and file changes.

Can I use it today?

You can build it from source or prepare an Arch package locally. There is no published release or update channel yet. Start with the alpha setup guide and review the remaining qualification gates before relying on it.

Which platforms are supported?

Arch / Omarchy on Hyprland Wayland is the alpha target. The X11 build has started under Xwayland, not a pure X11 session. Other Linux desktops are unverified; macOS and Windows are unsupported.

What do I need to run it?

A Wayland or X11 desktop, a Vulkan-capable GPU driver, and Node.js 22.19 or newer. Installed packages bundle Pi’s engine; source builds can use a compatible Pi checkout. See setup details.

Does everything run locally?

The app and engine run locally. Model-provider requests depend on your Pi configuration; tools run with the engine’s permissions and are not sandboxed by Pipkin.

Does it replace my editor or terminal?

No. It is a focused agent workspace with actions to open files in your editor or a terminal in your project.

Explore Pipkin’s source.

See the real implementation, current status, and open work in the public repository. There is no published download yet.