Skip to content
PiSharpPiSharp

Architecture

PiSharp is built as layered libraries. Each one depends only on the layers below it.

Layer Libraries
Contracts PiSharp.Contracts
Providers PiSharp.AI
Agent PiSharp.Agent, PiSharp.Tools, PiSharp.Sessions
Coding agent PiSharp.CodingAgent
Frontends PiSharp.Cli, PiSharp.Rpc, PiSharp.Tui
Extensions PiSharp.Extensions.Abstractions, PiSharp.Extensions.Runtime, PiSharp.Extensions.Agent, PiSharp.ExtensionHost, optional PiSharp.Compatibility.Node

Design principles

Section titled “Design principles”
  • Streaming is explicit. Transport fragments, incremental updates and committed messages are separate. A partial tool call is for display only; it can’t run until its arguments are fully parsed and validated.
  • Cancellation flows everywhere. Cancellation tokens reach every transport, tool and hook, and each operation ends in exactly one outcome.
  • Retries are safe. A provider retry never reruns a completed shell command or file change.
  • Sessions are append-only. The event log is the source of truth, and the current branch and context are built from it.

The full design is in docs/architecture.md, and the phased plans are in docs/plans.

PiSharp · MIT License. PiSharp is an independent port and not an official Pi release. Pi is created by Mario Zechner and maintained by Earendil; derived code keeps its MIT attribution.pi.dev