Pi

What Pi is

Pi is a terminal-first coding harness positioned as a minimal core that is extended through skills, extensions, prompt templates, themes, and installable packages.

Source: pi.dev, Pi documentation, earendil-works/pi

Why it is a candidate for Ikidna

Pi is a credible candidate for Ikidna for specific reasons:

Extensibility-first architecture. Pi is explicitly designed around a small core plus add-ons (skills, extensions, and packages). That maps well to Ikidna’s need to encode domain workflows instead of relying on fixed built-in behavior.

Programmatic control surfaces. Pi documentation exposes SDK, RPC mode, and structured JSON event-stream usage. This is directly relevant to Ikidna’s orchestrator-driven model, where harnesses must be controllable without manual terminal interaction.

Strong multi-model posture. Pi’s model catalog shows broad provider and model coverage, and the project frames itself around unified multi-provider model access. This aligns with Ikidna’s routing requirement to choose models by task, cost, and capability.

Ecosystem depth around agent operations. The package catalog shows a large ecosystem with packages for subagents, memory, policy/permission controls, MCP adapters, and orchestration patterns. For Ikidna, this suggests faster path-to-capability via extension composition rather than custom harness forks.

Open source maturity. Pi is MIT-licensed, actively released, and has a large contributor/user footprint. That lowers lock-in risk and improves the chance Ikidna can adapt internals if required.

Pi should therefore be treated as more than a placeholder candidate: it is a plausible primary harness option for a modular, orchestrated, multi-model Ikidna runtime.