create-agent-adapter

To create a new agent adapter package, you build a self-contained module under packages/adapters that implements server execute/parse logic, UI stdout parsing, and CLI formatters following shared adapter-utils contracts. You must export type, label, models, and agentConfigurationDoc from the root index file.

Building a Paperclip adapter requires structuring your package with dedicated server, ui, and cli modules, plus an index and tests. You must wire each module into its respective server, ui, and cli registries to ensure the runtime, UI config builders, and CLI formatters can consume the integration.

An agent adapter integrates with server execute and parse operations by implementing the required server-side interfaces defined in the shared adapter-utils contracts. This implementation handles command execution and parses the stdout output to ensure the server runtime can properly manage agent responses.

Yes, you need to write an agentConfigurationDoc when adding a new CLI integration. This descriptive documentation is required to guide LLM-based agents and must be exported from the package root alongside the adapter type, label, and models.

Yes, you can use existing adapters like claude-local and codex-local as an architectural blueprint. They provide clear guidance on the required module layout, registration points, and conventions needed to build a self-contained adapter package that exposes server, UI, and CLI integrations.

Building an adapter package without external dependencies requires strictly following the shared adapter-utils contracts for all TypeScript implementations. You must ensure proper registration paths in all server, UI, and CLI registries are maintained manually without external automation libraries.