Exporting Workspaces
"Export workspace zip," available from a project's menu, packages that project's workspace folder into a ZIP file at a destination you choose, using Android's document picker.
What gets exported
Export always covers the project's assigned workspace folder — not wherever a session's terminal happens to currently be, which matters if a session has been moved and shows a workspace mismatch warning.
What's excluded, and why
To reduce the chance of accidentally sharing credentials or bulky generated files, exports leave out paths such as .git, .ssh, agent-authentication and agent-state folders, node_modules, build/output directories, .env files, and files that look like private keys or contain "auth" or "token" in their path.
This exclusion list reduces risk — it does not eliminate it. It matches known patterns rather than scanning file contents for secrets. Always review an exported archive yourself before sharing it with anyone.
How export works internally
Deputy Shell first builds and verifies a complete ZIP in its own private storage, then copies that verified archive to the destination you picked. If that copy step is interrupted, see Export Recovery.
Limitations
Only one import or export can run per project workspace at a time.
Deputy Shell
Join Closed Alpha