pi-mono/packages/server

@earendil-works/pi-server

Experimental. This package is under active development and may change or be removed without notice. Its APIs and behavior are not yet stable.

Transport-neutral session server for pi.

Session server core

The package exports the PiServer session server and listener composition APIs.

import type { PiSessionBackend } from "@earendil-works/pi-server";
import { createUnixServer } from "@earendil-works/pi-server/unix";

const backend: PiSessionBackend = {
  async listSessions() {
    return storage.listSessions();
  },
  async listModels() {
    return modelRegistry.listModels();
  },
  async createSession(options) {
    return storage.createAndOpen(options);
  },
  async openSession(sessionId) {
    return storage.open(sessionId);
  },
};

const server = createUnixServer(backend, {
  path: "/tmp/pi/server.sock",
});
await server.start();

PiServer composes transport listeners through the PiServerListener interface. Each listener must complete any transport-specific authentication and authorization before passing a connection to PiServer. For example, a WebSocket listener can validate credentials during the HTTP upgrade, while the Unix listener relies on socket filesystem permissions. The Unix submodule exports the createUnixListener() building block and createUnixServer() preset, keeping the common case concise without coupling the primary server to Unix sockets. The listener uses length-prefixed CBOR messages from @earendil-works/pi-protocol. It does not yet replace the legacy JSONL IPC control plane, child-process supervisor, standalone server CLI, or Radius presence integration.

Transport testing

Custom transports can use @earendil-works/pi-server/testing for deterministic protocol conformance tests. It exports createTestServer(), TestSessionBackend, ProtocolTestClient, and the transport-neutral WireChannel contract. connectUnixTestClient() is provided for Unix transport tests.

pi-ai protocol bridge

@earendil-works/pi-ai domain objects and @earendil-works/pi-protocol wire DTOs remain independent. This package owns their boundary and exports toProtocolModelMetadata(), toProtocolAssistantMessage(), toProtocolUserMessage(), and toProtocolToolResultMessage().

The adapters reject invalid tool inputs, identifiers, timestamps, and mismatched tool results; toProtocolToolResultMessage() requires the original ToolCall so it can verify the association and convert its arguments itself. Diagnostic details are explicitly sanitized. Closed pi-ai unions are mapped exhaustively, and compile-time field manifests enumerate current pi-ai properties so additions require an explicit review. The protocol mirrors pi-ai vocabulary such as toolCall and toolUse where the semantics are identical. Protocol schemas enforce consistent lifecycle states, and tests encode adapter output through the runtime schemas so incompatible changes fail in the bridging package.