Export Apps as .tsk Files

Overview

A .tsk file is a single archive that holds your entire Taskade Genesis app: pages, components, agents, automations, and the Workspace DNA pointers that tie them together. It is the simplest way to back up a build, copy it to another workspace, or store it in a Git repo for safekeeping.

TL;DR: Open App Settings → Advanced → Code in any Taskade Genesis app and click Download .tsk. Drop the file into another workspace to restore the full app, including agents and automations. Encrypted secrets and DNS records stay local on purpose. Pair with GitHub export and import for ongoing version control.

Export an app

Pull a fresh archive whenever you ship a milestone, hand a build to another team, or want a checkpoint before a risky change.

1. Open the app you want to export.
2. Open App Settings, then choose Code under Advanced.
3. Click Download .tsk.
4. Save the file. You get a single .tsk download named after your app.

You can also grab it from the Publish dropdown in the app header, which offers the same Download .tsk option.

Downloading a .tsk file is available on Pro and above. On Free and Starter the option shows an upgrade badge instead.

Here is where the download lives inside App Settings:

┌────────────────────────────────────────────┐
│  App Settings  ›  Advanced  ›  Code        │
├────────────────────────────────────────────┤
│  Falcon CRM                                │
│                                            │
│  Download the full app as a .tsk bundle    │
│  to import into any Taskade workspace.     │
│                                            │
│  Includes  pages · agents · automations    │
│  Excludes  secrets · billing · DNS records │
│                                            │
│                         [ Download .tsk ]  │
└────────────────────────────────────────────┘

The archive captures the state at the moment you export. Future edits do not change the file you already saved.

What is inside a .tsk file

Open one in any unzip tool and you get a structured bundle. The runtime keeps it opaque so you do not have to think about internals.

• App pages and the layout that connects them
• Component graph (forms, tables, charts, embeds)
• Agent definitions and their memory pointers
• AI Teams, with the agents grouped into each one
• Automations, including triggers and action chains
• Theme, fonts, and brand styling
• GenesisAuth provider settings

Encrypted secrets, billing settings, and DNS records are deliberately excluded. They are workspace-bound and re-attached on the destination side.

Restore from .tsk

Restoring is a drag-and-drop. Taskade rebuilds the app, reattaches agents, and recreates automations behind the scenes.

1. Open the destination workspace.
2. Drop the .tsk file onto the workspace home or any folder.
3. Confirm the import. If a referenced agent or automation already exists, pick Merge to reuse the existing one or Replace to overwrite it.
4. Wait for the import status to flip to Ready.
5. Open the new app and check GenesisAuth, integrations, and any custom domains.

Restoring into the same workspace creates a copy. Restoring into a different workspace transfers ownership.

Check what your plan allows on import

There is no single gate on the file. Taskade checks each kind of item the file carries, and stops on the first one your plan does not cover.

Every check runs before anything is written, so a blocked import leaves your workspace untouched. Taskade names the item type that stopped it.

A kit built around projects and templates imports on any plan. A kit that carries automations or AI Teams needs the matching plan first. See pricing for current details.

Use with GitHub

Commit the .tsk file to a repo and you get full diff history of your app at the bundle level. Combine it with the two-way GitHub export and import flow for live source control across pages, components, and automations.

A common pattern:

• Export .tsk snapshots at every release.
• Use GitHub two-way sync for day-to-day edits and pull requests.
• Tag releases in Git with the .tsk artifact attached for easy rollback.

What does not transfer

A .tsk file is portable, not magic. A few items always need a fresh setup on the destination side.

• Encrypted credentials for connected services. Reconnect them in the new workspace.
• Billing and plan settings. They follow the workspace, not the app.
• Custom-domain DNS records. Add the domain again in the new workspace before publishing.
• App Users. Email-magic-link sessions stay tied to the original Space.

Re-set these after import and your restored app behaves exactly like the original.

Related guides

• GitHub Export and Import. Two-way source control for pages, components, and automations
• Builder Community & App Kits. Clone a published kit instead of restoring a file
• Version History. Roll an app back without leaving the workspace
• Publishing Taskade Genesis Apps. Take the restored app live again
• Multi-Agent Teams. What an imported AI Team can do