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.

Looking to run the agent live inside your own app instead of exporting it? See Integrate Agent.

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.

Export Agent is the export icon in the canvas header, between Integrate Agent and Agent Config.

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.

The Export Agent Package dialog.

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.

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.

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

I selected Export Package but no email has arrived

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.

The Download link in the email doesn't work

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.

An imported agent's MCP server shows Initialize

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.

I got a “Your agent export failed” email

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.

The imported agent has lost knowledge it had before

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.

Another agent's knowledge changed after I imported a package

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.

A governed graph is missing from the imported agent

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, then attach it to the agent. See Attaching a governed graph.

Images in the imported knowledge are missing

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.

FAQs

Can I download the package straight from the browser?

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

Is the agent's knowledge included in the package?

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.

Will re-importing the same package create duplicate knowledge?

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.

Are secrets included?

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.

Are MCP connections included?

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.

Who receives the export emails?

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

Related sections

• Integrate Agent — Run the agent live in your product instead of packaging it.
• Secrets & Variables — Recreate or rotate secret values in the target environment.
• Runtime & Versioning — Match runtime settings after import.

---

Maintained by Abhishek Paul AI-assisted, human-approved