Skip to main content

​
Export & import agents

An agent’s full configuration can be exported as a portable package (a JSON file) and imported into another tenant — useful for promoting an agent from a sandbox tenant to production, sharing a build between teams, or keeping an offline copy of a known-good configuration. Both directions require the Admin or Owner role.

​
Export

On the agent’s Profile page, click Export. The download contains:
  • The agent’s profile — name, role, personality, safety boundaries, language policy, greetings, and guidance.
  • Its skillsets, with their skills and configurations.
  • Its widget appearance settings (branding, greeting, identity mode).
Secrets are never exported. Skillset credentials, OAuth tokens, and provider secrets are stripped or blanked; the package carries only a hash of the source tenant, never the tenant itself. A package is safe to store and share within your organization, but treat it as configuration — anything secret must be re-entered at the destination.

​
Import

On the Agents page, click Import and choose the package file. Cobalt validates it and shows a preview — each profile field, configured or empty — before anything is created. If an agent with the same name already exists, you choose:
  • Create as new — import alongside the existing agent.
  • Update existing — overwrite the existing agent’s profile with the package, shown side-by-side first so you can compare.

​
After an import

  • The agent is created through the normal path (including its test/preview widget) and you land on its Profile page.
  • Skillsets, skills, and configurations arrive with their exported active state — but any secret values are empty and must be re-entered before those skills work.
  • Integrations are not recreated by import today. The export records them for reference; reconnect and re-authorize integrations by hand at the destination (authorization is tenant-specific by design).