> 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/agent-builder/deploy/export-agent.md).
# Export Agent
**Export Agent** captures everything that defines an agent as a portable bundle you can move between environments or hand to another team. Find it under **Manage Agent → Export Agent**.
{% hint style="info" %}
Looking to run the agent live inside your own app instead of exporting it? See [Agent Integration](/agent-builder/deploy/agent-integration.md).
{% endhint %}
Export Agent Package is the top row of the screen; click the chevron to open the export dialog.
## 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
* 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, two toggles decide how much sensitive material travels inside the bundle. Both are **off by default**, so the base package carries only the agent's logic and configuration.
The Export Agent Package dialog.
| Option | Default | What it includes |
| ----------------------------- | ------- | ----------------------------------------------------------------------------------- |
| **Include secrets** | Off | The agent's actual API keys, tokens, and credentials — not just references to them. |
| **Include MCP configuration** | Off | The agent's MCP server connections and tool configuration. |
{% 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. Click the chevron (`>`) on the **Export Agent Package** row to open the dialog, set **Include secrets** and/or **Include MCP configuration** as needed, then click **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
* [Agent Integration](/agent-builder/deploy/agent-integration.md) — Run the agent live in your product instead of packaging it.
* [Secrets & Variables](/agent-builder/build/secrets-and-variables.md) — Recreate or rotate secret values in the target environment.
* [Runtime & Versioning](/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/agent-builder/deploy/export-agent.md?ask=&goal=
```
`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.