pi-cordis

Integrating the Pi coding agent into an ACRYL runtime previously meant handing over application composition and lifecycle ownership to Pi, leaving the host unable to mount, swap, or clean up the engine at will. pi-cordis packages Pi as a standard Cordis runtime plugin, exposing a Pi SDK session through the host's existing Cordis tree so that Pi remains a pluggable engine provider rather than the owner of application composition.

The plugin exposes a single ctx.piEngine surface. Consumers interact with Pi's agent loop, model runtime, session operations, and event stream through this interface without ever creating or retaining Pi SDK sessions directly. Service mounting, unmounting, subscription management, fiber-disposal cleanup, and hot replacement are all owned by the Cordis host. This separation lets a host observe, remove, or swap Pi without rewriting any downstream consumer code, and a persistent flag lets you choose between in-memory sessions and disk-backed storage in the configured working directory.

If you are building a multi-engine ACRYL runtime that relies on Cordis for dependency management and lifecycle control, and you want to bring Pi's coding-agent capabilities into the same host with minimal coupling and a clean boundary, pi-cordis is the integration layer that slots Pi into your existing composition tree.