Exporting and importing assistants

When you set up a new environment, or promote an assistant from staging to production, you rarely want to recreate it from scratch. Ajutant can export an assistant to a portable, signed file (an .ajutant bundle) and import that file into another environment, so the whole assistant moves in one step.

The bundle carries the assistant’s configuration: its name and description, its system prompt, its model tier, its knowledge base references, and any API endpoints it exposes. It never carries API keys or other secrets. Each environment keeps its own keys, so you mint those again after import.

What travels in a bundle

• The assistant’s system prompt and settings.
• Its model tier, not a fixed model name, so the target environment picks one of its own approved models.
• Knowledge base entries and website references.
• Any API endpoints, with their input and output shapes.

What does not travel: API keys, connection credentials, and anything else specific to one environment. You add those in the target after import.

Export

1. Open the assistant you want to move, then choose Export.

2. Ajutant produces a signed .ajutant file and downloads it. The signature lets the target environment confirm the bundle came from a source it trusts.

3. Keep the file somewhere safe. It is a snapshot: export again whenever the assistant changes.

Note

A bundle is signed by the source environment. Before another environment will import it, that environment must trust the signing key. See Trusting a bundle with signing keys.

Import

1. In the target environment, open Admin, then Import.

2. Choose the .ajutant file. Ajutant checks the signature against the signing keys the environment trusts, then reads the assistant it contains.

3. Review what will be created, including how the model tier maps to a model in this environment, then confirm.

4. Add anything the bundle deliberately left out: mint an API key for each endpoint, and connect any external systems the assistant uses.

Keeping environments in step

A bundle is a point-in-time snapshot. When the source assistant changes, export it again and re-import it in the target. Because the bundle references a model tier rather than a fixed model, the same file works across environments that map tiers to different models.

Building or inspecting bundles directly? The .ajutant bundle format reference describes the file’s envelope, payload, versioning, and what does and does not travel.