Skip to main content

Exporting and importing agents

You can export an entire agent—including its tools, user inputs, flows, data sources, and settings as a portable JSON file. Share it with teammates, move it between environments, or keep it as a backup. You can also encrypt the bundle with a passphrase for secure sharing.

Exporting an agent​

  1. Open the agent you want to export in the editor.
  2. Click Manage > Export in the toolbar.
  3. Choose which data sources to include. Agent configuration, tools, user inputs, and flows are always included.
  4. Optionally, enter an encryption passphrase to protect the bundle.
  5. Click Export (or Encrypt & Export if using a passphrase).

The bundle is downloaded as a .json file. If you set a passphrase, the file is saved as .encrypted.json instead.

Note: Sensitive information such as API keys, OAuth credentials, and passwords are removed from the export automatically. After import, people are prompted to add their own credentials.

Importing an agent​

  1. From the agent creation screen, click Import Agent.
  2. Select a .json bundle file. If the file is encrypted, a passphrase field appears automatically.
  3. Enter the passphrase (if prompted) and proceed.
  4. Review and customize:
    • Override the agent name if needed
    • Toggle data source inclusion
    • Provide any required credentials that were removed during export
  5. Click Import to create the new agent.

What happens to data sources?​

  • Same environment: If the original data source still exists and you can access it, the imported agent links to it directly. Data sources are not duplicated.
  • Different environment: If the data source does not exist or belongs to another organization, the platform creates a new data source from the content included in the bundle.

What happens if the language model is not available?​

If the model used by the original agent is not available in your environment, the platform substitutes an available model and shows a warning. You must confirm that the substituted model meets your needs.

Providing credentials after import​

When an exported bundle includes tools that used API keys or other secrets, the import modal shows a field for each one. For example:

  • API key for "Weather" tool
  • OAuth client secret for "GitHub" tool
  • Database password for "Analytics" tool

You can fill these in during import or leave them empty and configure them later in the agent's tool settings.

Bundle encryption​

Encryption runs entirely in your browser; the passphrase never leaves your device.

  • The bundle is encrypted with AES-256-GCM, a strong authenticated encryption standard.
  • If you forget the passphrase, the bundle cannot be recovered. Store it securely.

Good to know​

  • Secrets are never exported. API keys, passwords, and other credentials are removed from the bundle automatically. Anyone importing the agent must supply their own.
  • Cloud data source connections are not preserved across environments. When you import into a different organization, live connections to services such as Google Drive or Confluence are not carried over. Only file content from those sources is included.
  • Model substitution may occur. Confirm that the language model assigned after import is the one you want.
⌘J