> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/deploy/export-agent.md).

# Export Agent

Bundle an agent's full configuration into a portable, reusable package.

**Export Agent Package** bundles this agent's logic, configuration, tools, and contextual data into a single portable package for reuse or deployment in another environment. Open it with **Export Agent**, the export icon in the header above the canvas, between **Integrate Agent** (`</>`) and **Agent Config**. You need the **Export Agent** capability; without it the button is disabled.

{% hint style="info" %}
Looking to run the agent live inside your own app instead of exporting it? See [Integrate Agent](/ai-workbench-qore/console/agent-builder/deploy/agent-integration.md).
{% endhint %}

You can also open it from the agent list: in **My Agents**, select **•••** on the agent's row, then **Export Agent**. It opens the same dialog.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-747fb7b94642d29435df007d3b534debaf895025%2Fqore_agent-builder_how-to-canvas-header_rounded_shadow.png?alt=media" alt="The canvas header: the Overview and Flow tabs, credits and cost, the Draft Version selector, the Integrate Agent and Export Agent icons, Agent Config, and Try Agent"><figcaption><p>Export Agent is the export icon in the canvas header, between Integrate Agent and Agent Config.</p></figcaption></figure>

## What gets exported

The bundle is a complete snapshot of the agent's setup, so it can be rebuilt exactly as-is somewhere else. It includes the agent's:

* Identity and instructions
* Attached skills and knowledge
* Integration skills
* Triggers and checklists
* Guardrails
* Runtime settings

That makes it useful whenever the agent needs to leave its current home:

* Move it between environments (development → staging → production)
* Share it with another team or tenant
* Keep a portable backup outside the platform

## Knowledge in the package

Knowledge attached to the agent always travels with it. No export option turns it off. The package holds each knowledge base attached to the agent, together with its files.

When you import the package, Qore restores each knowledge base, with its files, into the importing project as that project's own copy, and attaches it to the imported agent. Each restored knowledge base gets a new version labelled *Imported*.

* **Re-importing** the same package updates the project's existing copy instead of making a second one. Other agents in that project that use the same knowledge base see the update too.
* **Knowledge that another project already holds** is imported as a new copy. The original isn't changed.
* **An import replaces the agent's knowledge rather than adding to it.** Knowledge the agent already had in the target project, but that isn't in the package, is detached. Governed graphs stay attached.
* **Governed graphs aren't imported.** The import lists them in a warning: *N attached knowledge graph(s) will not be imported*, followed by their names.
* **Older multimodal knowledge comes back as text.** Files that were ingested as multimodal are imported and processed as text only. The import warns you how many are affected.

## Export options

Before you export, three checkboxes decide how much sensitive or connected material travels inside the bundle. All three are unchecked by default.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-73daf3367727e4e43e6a457e38227c67dd85f625%2Fqore_agent-builder_how-to-export-agent-package_rounded_shadow.png?alt=media" alt="The Export Agent Package dialog: Export this agent&#x27;s logic, configuration, tools, and contextual data into a single portable package, with Include secrets, Include MCP configuration and Include integration skills checkboxes, and Cancel and Export Package buttons"><figcaption><p>The Export Agent Package dialog.</p></figcaption></figure>

| Option                         | Default   | What it includes                                                                                |
| ------------------------------ | --------- | ----------------------------------------------------------------------------------------------- |
| **Include secrets**            | Unchecked | API keys, tokens, and credentials — not just references to them.                                |
| **Include MCP configuration**  | Unchecked | Each MCP connection's credentials and settings: OAuth client ID and secret, headers and tokens. |
| **Include integration skills** | Unchecked | The agent's connected Apps & Services / integration-backed skills and their setup.              |

Ticking any of the three shows a warning: *Exporting secrets, MCP configuration, or integration skills may expose sensitive credentials, internal tools, or privileged access.*

**MCP connections are exported either way.** With **Include MCP configuration** on, each connection travels with its credentials and settings, ready to use. With it off, each connection travels without its OAuth client ID and secret, headers and tokens, and is marked not initialized. After import, such a connection shows **Initialize** in the agent: select it to re-enter the connection's credentials. See [MCP](/ai-workbench-qore/core-concepts/mcp.md#managing-a-connection).

{% hint style="warning" %}
**Include secrets exports credential values in plaintext form inside the package.** Leave it off unless the destination environment genuinely needs the same credentials and the package will be handled securely. When it is off, secrets export as references and you supply the values again in the target environment via **Secrets & Variables**.
{% endhint %}

## Exporting the package

With your options chosen, the export itself is a single step. Select **Export Agent** in the header, set **Include secrets**, **Include MCP configuration**, and **Include integration skills** as needed, then select **Export Package** (or **Cancel** to dismiss).

The package isn't downloaded in your browser. Qore builds it in the background, so a large agent can't time out while you wait, and shows *Agent export is in progress. You will receive an email with the download link shortly.*

When the package is ready, you get an email titled *Your agent export "‹agent name›" is ready!* Select **Download** in the email to get the package, the one portable file you import into another environment. If the export raised any warnings, the same email lists them after *Please note:*.

The download link expires. How long it lasts depends on where your deployment stores files. Exporting the agent again sends a new email with a new link.

If the export fails, Qore retries it automatically. If it still fails, you get an email titled *Your agent export failed* that gives the reason, and a **View Agent** button that opens the agent. The email ends with *If the issue persists, please contact support*, followed by a reference ID to share when one is available.

Both emails go to the email address of the user who started the export.

## Troubleshooting

<details>

<summary>I selected Export Package but no email has arrived</summary>

The email is sent only when the package has finished building. It goes to the email address of the user who started the export. If the export fails, that address gets a *Your agent export failed* email instead.

</details>

<details>

<summary>The Download link in the email doesn't work</summary>

The download link expires, and how long it lasts depends on where your deployment stores files. Exporting the agent again sends a new email with a new link.

</details>

<details>

<summary>An imported agent's MCP server shows Initialize</summary>

The package was exported without **Include MCP configuration**, so the connection has no credentials. Open it, select **Initialize**, and enter them. See [Managing a connection](/ai-workbench-qore/console/agent-builder/build/mcp-tools.md#managing-a-connection).

</details>

<details>

<summary>I got a “Your agent export failed” email</summary>

Qore sends this email after retrying the export automatically. The email gives the reason the export failed, and **View Agent** opens the agent. The email ends with *If the issue persists, please contact support*, followed by a reference ID to share when one is available.

</details>

<details>

<summary>The imported agent has lost knowledge it had before</summary>

An import replaces the agent's knowledge rather than adding to it. Knowledge the agent had in this project that isn't in the package is detached. The knowledge base itself isn't deleted, so you can attach it again. See [Attaching Knowledge to an Agent](/ai-workbench-qore/console/agent-builder/build/attaching-knowledge-to-an-agent.md).

</details>

<details>

<summary>Another agent's knowledge changed after I imported a package</summary>

Re-importing a package updates this project's copy of each knowledge base in it, and every agent in the project that uses that knowledge base sees the update.

</details>

<details>

<summary>A governed graph is missing from the imported agent</summary>

Governed graphs aren't imported. The import lists them in a warning that starts *N attached knowledge graph(s) will not be imported*. Upload the graph in the target environment's [Governed Graph](/ai-workbench-qore/control-center/govern/governed-graph.md), then attach it to the agent. See [Attaching a governed graph](/ai-workbench-qore/console/agent-builder/build/attaching-knowledge-to-an-agent.md#attaching-a-governed-graph).

</details>

<details>

<summary>Images in the imported knowledge are missing</summary>

Knowledge that was ingested as multimodal comes back as text only, because multimodal ingestion has been removed. The import warns you how many files are affected.

</details>

## FAQs

<details>

<summary>Can I download the package straight from the browser?</summary>

No. The package is always built in the background and delivered by email, so a large agent can't time out while you wait.

</details>

<details>

<summary>Is the agent's knowledge included in the package?</summary>

Yes, always. Each knowledge base attached to the agent travels with it, together with its files, and no export option turns this off. See [Knowledge in the package](#knowledge-in-the-package).

</details>

<details>

<summary>Will re-importing the same package create duplicate knowledge?</summary>

No. Re-importing updates the project's existing copy of each knowledge base. Knowledge that another project already holds is imported as a new copy, and the original isn't changed.

</details>

<details>

<summary>Are secrets included?</summary>

Only when you turn on **Include secrets**, which is off by default, and then their values are in the package in plaintext. Otherwise secrets export as references, and you enter the values again in the target environment's **Secrets & Variables**. See [Export options](#export-options).

</details>

<details>

<summary>Are MCP connections included?</summary>

Yes, always. **Include MCP configuration**, off by default, decides whether each connection's OAuth client ID and secret, headers and tokens go too. Without them, the connections arrive needing **Initialize**. See [MCP Tools](/ai-workbench-qore/console/agent-builder/build/mcp-tools.md#exporting-and-importing).

</details>

<details>

<summary>Who receives the export emails?</summary>

The user who started the export, at their account's email address. Both the ready email and the failure email go there.

</details>

### Related sections

* [Integrate Agent](/ai-workbench-qore/console/agent-builder/deploy/agent-integration.md) — Run the agent live in your product instead of packaging it.
* [Secrets & Variables](/ai-workbench-qore/console/agent-builder/build/secrets-and-variables.md) — Recreate or rotate secret values in the target environment.
* [Runtime & Versioning](/ai-workbench-qore/console/agent-builder/build/runtime-and-versioning.md) — Match runtime settings after import.

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/deploy/export-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.