create-agent-adapter

To build a Paperclip agent adapter, create a self-contained package under packages/adapters/<name>/ and implement server, UI, and CLI modules following the architecture blueprint. You must provide mandatory exports including type, label, models, and agentConfigurationDoc for end-to-end integration.

Exposing server and CLI integrations requires exporting type, label, models, and agentConfigurationDoc metadata. The adapter package must also follow standard registration points and conventions to ensure proper architecture and session handling across different runtimes.

Yes, you can use this architecture to create adapters for Claude Code, Codex, or custom processes. The blueprint supports multiple runtimes by standardizing file structure, session management, environment rendering, and prompt templates across different agent integrations.

A production-ready agent adapter package uses the structure packages/adapters/<name>/ containing server, UI, and CLI bindings. It organizes architecture, registration points, metadata exports, and skill registration patterns to ensure a complete end-to-end integration.

Session handling and environment rendering in a Paperclip adapter manage runtime contexts and render prompt templates for the target agent process. The blueprint architecture defines these conventions to maintain consistent state across server, UI, and CLI integrations.