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 Settings → Export in any Taskade Genesis app and pick .tsk archive. 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.
- Open the app you want to export.
- Click Settings in the right rail.
- Pick Export.
- Choose .tsk archive as the format.
- Save the file. You get a single
.tskdownload named after your app.
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
- 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.
- Open the destination workspace.
- Drop the
.tskfile onto the workspace home or any folder. - Confirm the import. If a referenced agent or automation already exists, pick Merge to reuse the existing one or Replace to overwrite it.
- Wait for the import status to flip to Ready.
- Open the new app and verify GenesisAuth, integrations, and any custom domains.
Restoring into the same workspace creates a copy. Restoring into a different workspace transfers ownership.
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
.tsksnapshots at every release. - Use GitHub two-way sync for day-to-day edits and pull requests.
- Tag releases in Git with the
.tskartifact 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.