create-agent-adapter

To build a Paperclip adapter, create a new package under packages/adapters following the four-export layout that provides server, UI, and CLI integrations. You must define required exports including type, label, models, and agentConfigurationDoc to establish the connection.

The required module structure for a Paperclip agent adapter consists of a four-export package layout powering server, UI, and CLI integrations. This structure must wire environment setup, session management, prompt rendering, process spawning, and stdout parsing into the registry.

Yes, your custom adapter should preserve compatibility with claude-local and codex-local patterns. The blueprint outlines specific registration conventions and required exports that ensure your new runtime integrates consistently with the existing orchestration layer.

You wire session management and prompt rendering by implementing the end-to-end adapter lifecycle modules. This lifecycle covers environment setup, session management, prompt rendering, process spawning, stdout parsing, and metadata emission for runtime artifacts.

Yes, you can integrate a custom process by creating a new adapter package that follows the provided skeleton. The pattern supports adding support for a new AI coding tool, integrating a custom process, or extending an existing adapter family.

When extending an existing Paperclip adapter family, you must preserve compatibility with established claude-local and codex-local patterns. Deviating from the required exports, module structure, and registration conventions will break the orchestration layer.