5 exports to test before choosing an AI workspace
Check whether code, data, context, configuration, and task evidence remain useful when you leave an agent workspace.
Maintained by the Matrix OS team. Product instructions are updated with the supported workflow.
You can clone the repository somewhere else. Great. Can you also recreate the database, find the decisions behind the code, and run the application without spending an afternoon remembering what you installed?
A useful workspace export includes code, data, configuration, and enough instructions to resume work elsewhere. Test a restore before you need one. Owning the files matters most when you can actually use them.
The export checklist
| Asset | What to retain | Verification |
|---|---|---|
| Code | Repository and uncommitted work | Open it elsewhere and inspect the diff |
| App data | Database export and schema | Restore a sample in a separate environment |
| Context | Reviewed briefs and decision notes | Another agent can identify the next task |
| Configuration | Dependency manifests and setup instructions | Reproduce the test command |
| Evidence | Logs, reports, and accepted test results | Trace a conclusion back to its input |
Code is only one part of the project
A Git push may preserve source but omit uploaded files, a local database, and untracked notes. Inventory those separately. Use sample data for a restore test so you can validate the process without moving sensitive production information.
Keep secrets out of an export intended for a new tool. Record the names of required connections and authentication steps, not raw tokens. Reauthorize through the destination's supported flow.
Context should survive the agent
Keep important decisions in files you can read and move. Record what you chose, why you chose it, and which source supports the decision. Include known failures and the next unfinished task.
The next agent should not have to infer the project history from a pile of chat messages. Neither should you. A short, reviewed handoff document is often enough to save an expensive round of rediscovery.
When to use Matrix OS vs a task-only workflow
Matrix offers owner-controlled and exportable files, database, and runtime in a retained workspace. That is relevant when the project spans multiple agent sessions and tools. A provider task workflow can be sufficient when the complete deliverable is a repository change and its review evidence.
Do not assume a task service's exported branch includes every artifact you care about. Ask the service to demonstrate its export path, just as you would for Matrix.
Budget the exit test
Pick a small project and restore it into another environment. Install its dependencies, load a safe data copy, and run its documented checks. Record every missing step while it is fresh.
Count the time it takes to get a working application, not just the time it takes to download an archive. That is the practical measure of whether your export process works.
FAQ
Does exportability mean every provider conversation transfers?
No. Distinguish your project files from provider-held conversation history and account data.
Should I export the whole runtime?
First identify what you need to reproduce. A documented setup plus code and data may be more usable than an opaque machine copy.
What counts as success?
A fresh environment can run the sample project, read the handoff brief, and reproduce the relevant check. See the Matrix architecture for ownership context.
This is a Matrix OS guide, reviewed October 20, 2026. We compare documented capabilities and explain our recommendations; we have not benchmarked these products against each other. Agent usage is separate from workspace pricing unless stated otherwise.
Start with one real task
Get your Matrix. Visit the homepage to download Matrix OS Desktop for macOS, Windows, or Linux. Start with one repository and one bounded task. The first eligible primary computer has a 3-day free trial; a card is required and billing starts unless you cancel before renewal. Review current plans.