Skip to main content

Bundles

A bundle is a JSON file containing a manifest of resources — your selection plus everything it depends on — with all secrets stripped. Export one from your company, hand the file to anyone, and they import it into theirs.

What it's for​

Bundles are the private, no-review way to move work between companies: cloning a workflow into a client's workspace, migrating between environments, or sharing a setup with a partner without publishing it publicly. The same bundle format also powers catalog templates, so everything on this page applies there too.

From Marketplace in the sidebar, choose Export bundle or Import bundle on the landing page. Past and in-progress installations live under the installation detail pages, reachable from the landing page's Recent installs feed.

Key concepts​

  • Manifest — the bundle file (autessa-bundle-<timestamp>.json) contains every resource definition, the dependency graph between them, connector requirements, and a record of which secret fields were stripped.
  • Dependency auto-resolution — the export walks references transitively: a manager pulls in its agents, an agent pulls in its tools and MCP server, a tool pulls in the table it queries, and so on. Auto-included resources are shown separately from your explicit selection and can be unchecked to drop them (and their own dependents) from the bundle.
  • Secrets stripping — MCP server auth configuration and connector credentials/OAuth state are removed at export. The receiving company re-supplies them at import; connectors specifically can never be recreated from a bundle and must be linked to an existing authenticated connector on the target side.
  • Limits — a bundle holds at most 200 resources, and the dependency graph may be at most 8 levels deep. Exceeding either fails the export with a message to narrow the selection or split the bundle. Custom apps must have a published version; the export pins each app to its latest published version.
  • Install saga — imports create resources dependencies-first, committing each step individually. On failure, everything already created is rolled back and the install is marked failed with an error log.

How to export a bundle​

  1. Open Marketplace → Export bundle.
  2. Pick resources — filter by type in the left rail, search by name or description, and select the resources you want. The summary rail tracks your running total and reminds you that dependencies are pulled in automatically. Click Continue to review.
  3. Review & export — the preview splits the bundle into You selected and Auto-included as dependencies. Uncheck any auto-included resource you don't want to ship.
  4. Click Download bundle to save the JSON file (or Publish to marketplace to turn the same selection into a catalog template instead).

How to import a bundle​

  1. Open Marketplace → Import bundle and upload the .json file (drag and drop or browse).
  2. Review — the wizard lists everything inside, grouped by type, and how many resources will install into your company.
  3. Dependencies — for each resource, choose Create new (the default) or Link to existing if you already have an equivalent; the picker shows match confidence. Connectors must be linked to an existing, authenticated connector — if you don't have one, the wizard deep-links to the connector's setup page, and you can't proceed until every connector is linked.
  4. Supply credentials — enter values for each stripped secret field, or leave them blank to configure later (MCP server auth, for example, can be finished afterwards on the MCP Servers page).
  5. Install — the install runs automatically with a live per-resource timeline. Linked resources complete instantly; created resources appear as they commit. Newly created tools, agents, managers, and custom apps are published automatically when the install finishes.

How to track an installation​

  1. Open the installation from Recent installs on the Marketplace landing page (or from the import wizard's final screen).
  2. While the install runs, the page polls live: each resource shows Creating…, then Created with a link to its editor, or Linked if you mapped it to an existing resource.
  3. If the install fails, the error log is shown and each created resource reads Rolled back — your company is left in the state it was before. Fix the cause (most often a missing connector or invalid secret) and re-import.
  4. On success, a share card appears — see below.

How to share installed resources​

Completed installations offer sharing without leaving the status page:

  1. Use the per-resource Share button, or the bulk Share these resources? card for the whole install.
  2. Choose Share with company (read-only), Share with company (can edit), or Keep private; the bulk card can also share with specific teammates with read or write access.
  3. MCP servers and connectors are excluded — MCP servers are company-wide by construction, and connectors are gated by their own credentials.
To share a single resource with another company rather than your own team, export it as a one-resource bundle: the export wizard accepts a single seed resource and will pull in only what it needs.