Pi Web UI — AI skill for Claude Code

Pi Web UI

**A standardisation layer for coding agents: one session model and one local API across Pi Coding Agent, Claude Code, OpenCode, Antigravity and Command Code — so a parent agent can orchestrate children on any harness. It also comes with a browser UI over the same sessions.**

I use it mostly as an orchestration layer now. A strong model in one harness plans the work and fans it out to cheaper children running in *other* harnesses, waits without burning tokens, reads normalised results and checks them before accepting. The browser UI is where it started, and I still use it, but less and less.

It is a working personal system made public. It is messy in places and honest about it, and it is meant to be adopted piece by piece.

**It works because of the whole set, not the API alone.** The Internal API is used with a thin client ([`pi-orch`](https://github.com/valtterimelkko/pi-orch)), four orchestration skills ([the pack](https://github.com/valtterimelkko/agent-workflow-skills/blob/main/packs/pi-web-ui-orchestration-pack/README.md)) and the [watch-wake companions](https://github.com/valtterimelkko/agent-workflow-skills/tree/main/companions/watch-wake) that wake an idle parent when a child finishes, at zero token cost. Those are the reason a parent can supervise several children for hours without watching them. Take all of it: [`docs/ORCHESTRATION-FIXTURE-SET.md`](./docs/ORCHESTRATION-FIXTURE-SET.md).

**New here?** Read [`docs/ORCHESTRATION-OVERVIEW.md`](./docs/ORCHESTRATION-OVERVIEW.md) (what it is, how I use it, how to adopt it), then [`docs/INTERNAL-API-QUICKSTART.md`](./docs/INTERNAL-API-QUICKSTART.md) for a first call.

What it does

• Multi-harness, multi-runtime orchestration. A parent creates, prompts, watches, reads and verifies child sessions across five harness families through one local HTTP API (a Unix socket on the same machine). The parent can be any of them; mine is usually Claude Code.
• One session model. One registry, one