Export & Import
Once you've built a company — given it a goal, hired agents, configured their adapters, and set up projects — that configuration has real value. Export and import let you capture that configuration a…
Export & Import
Once you've built a company — given it a goal, hired agents, configured their adapters, and set up projects — that configuration has real value. Export and import let you capture that configuration as a portable package you can back up, share with others, or reuse as a starting point for a new company.
Exports are human-readable markdown files. Anyone with the package can understand the company's structure without reading a database dump.
---
What a package contains
An exported company package looks like this:
my-company/ ├── COMPANY.md ← Company name, goal, and metadata ├── agents/ │ ├── ceo/AGENT.md ← Agent identity, role, and instructions │ └── cto/AGENT.md ├── projects/ │ └── main/PROJECT.md ├── skills/ │ └── review/SKILL.md └── .paperclip.yaml ← Adapter types, environment variable declarations, budgets
What's included: Company name, description, and goal. Agent names, roles, reporting structure, and instructions. Project definitions. Skills. Adapter type declarations and the names of environment variables that need values.
What's never included: Secret values — API keys, tokens, passwords. Machine-specific paths. Internal database IDs. These things are environment-specific and wouldn't be valid on another machine anyway.
---