> 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/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 from the export icon in the top toolbar, next to the Draft Version selector.

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

## 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

## Export options

Before you export, three checkboxes decide how much sensitive or connected material travels inside the bundle. **Include secrets** and **Include integration skills** are unchecked by default; **Include MCP configuration** is checked by default.

| Option                         | Default   | What it includes                                                                   |
| ------------------------------ | --------- | ---------------------------------------------------------------------------------- |
| **Include secrets**            | Unchecked | API keys, tokens, and credentials — not just references to them.                   |
| **Include MCP configuration**  | Checked   | The agent's MCP server connections and tool configuration.                         |
| **Include integration skills** | Unchecked | The agent's connected Apps & Services / integration-backed skills and their setup. |

{% 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. Open the export icon in the top toolbar, set **Include secrets**, **Include MCP configuration**, and **Include integration skills** as needed, then select **Export Package** (or **Cancel** to dismiss). The platform bundles the agent's configuration into one portable file you can import into another environment.

### Related sections

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.