pi.harness

Agent harness

A harness with the seams showing.

Four published packages instead of one opaque product: a provider API, an agent runtime, a terminal UI, and the coding agent CLI built on top of them.

Stated plainly by the project

Pi has no built-in permission system for filesystem, process, network or credential access. It runs with the permissions of whoever launched it, and the docs describe three containerization patterns for stronger boundaries.

Package layoutMIT licensed
pi-coding-agent

Coding agent CLI

The interactive agent you run in a terminal.

pi-tui

Terminal UI

A rendering library with differential updates.

pi-agent-core

Agent runtime

Tool calling and state management for the loop.

pi-ai

Unified provider API

One interface across OpenAI, Anthropic, Google and others.

*

Take one layer. Each package is published on its own, so the provider API or the runtime can be used without adopting the CLI above it.

Where the boundaries are drawn

Sandbox is explicit

Isolation comes from a micro VM, plain Docker, or a policy-controlled sandbox, not from the harness itself.

Dependencies are reviewed

The project treats npm dependency changes as reviewed code changes, with direct dependencies pinned.

Builds are reproducible

Release archives ship with checksums and a build script for standalone binaries.