create-agent-adapter

Building a Paperclip adapter involves implementing a self-contained TypeScript package that bridges your AI agent runtime to Paperclip's orchestration. You implement server, UI, and CLI modules, standard parsing, execution, and session management within a conventional package layout.

A Paperclip adapter is a standardized bridge connecting a chosen AI agent runtime to Paperclip's orchestration layer. You need one to enable consistent interfaces, registries, and deployment workflows across server, UI, and CLI integrations for your specific agent.

Yes, this adapter blueprint supports connecting standard runtimes like Claude Code or Codex CLI, as well as custom processes. It provides a shared metadata contract and conventional package layout to ensure predictable integration and deployment across any runtime.

Adapter development requires implementing server parse/execute logic, UI parsing, CLI formatters, and a session codec. You must also export shared metadata including type, label, models, and agentConfigurationDoc, alongside environment injection and adapter registration.

Session management in a Paperclip adapter uses a session codec to handle state persistence and retrieval. The blueprint provides guidance on implementing this codec alongside environment variable injection and skill injection patterns for your agent runtime.

The best way to structure a Paperclip integration package is to follow the conventional layout provided, placing the adapter under packages/adapters. This structure separates server, UI, and CLI modules while standardizing exports for predictable deployment and registration.