What is pitty?

PiTTy is a separate, fast terminal interface built for a coding agent called Pi. Rather than being an extension that plugs into Pi's existing terminal screen, PiTTy replaces that whole screen with its own scrollable, more inspectable interface, while still using Pi underneath for the actual agent work: its logins, providers, models, sessions, tools, skills, prompt templates, and extensions all stay the same. Installing PiTTy is a single command on Linux, macOS, or WSL, or a PowerShell script on Windows. It requires Node.js 22.19 or newer, npm, and the Pi CLI already installed. The installer checks these requirements, downloads a specific release, verifies it against a published checksum, sets up PiTTy's own local Bun runtime, and creates launcher commands called pitty and pitty resume. Installing PiTTy does not replace or interfere with a normal Pi installation, so both can be used side by side. The reason to use PiTTy instead of Pi's built in terminal comes down to a handful of things: it lets you inspect subagent conversations separately from the main chat, control work while it is running by sending steering messages or pausing tasks, keep the visible workspace calmer since the prompt stays fixed while the conversation scrolls on its own, show clearer diff views when code changes are made, and search through past sessions and models more easily. PiTTy is written in TypeScript, using a library called OpenTUI together with SolidJS for a declarative, reactive interface, and it runs on a local Bun runtime. It aims to support Pi's existing ecosystem of commands, tools, prompt templates, and skills rather than create a separate incompatible one, though some highly customized visual extensions in Pi cannot yet be shown exactly as they appear in Pi itself, and Pi's login flow still needs to be completed in regular Pi. The project is licensed under MIT, so it can be used, modified, and shared freely, including for commercial purposes.