Persistent Workspace

​

Overview

Every SYMI session works against a workspace: a set of files SYMI can read, create, and modify on your behalf. Not everything in that workspace has the same lifespan — some files are meant to last only as long as the current conversation, and others are designed to survive session close, and even a platform restart. Understanding the difference matters mainly for one question: if I close this chat and come back later, will this still be here?

​

What persists, and what doesn’t

​

Project files

Project files are the durable part of your workspace. When SYMI creates a document, a script, or another output and you indicate you want to keep working with it, it lives in your project area rather than disappearing with the session. This is what lets you pick up a task days later without re-uploading everything or re-explaining your setup.

​

Task workspaces

Longer-running tasks get their own working area, separate from your everyday project files. This keeps in-progress work for a substantial task — intermediate files, drafts, scratch output — from cluttering your main workspace while the task is underway. A task workspace has its own lifecycle tied to that task, distinct from your ongoing project files.

​

Where this fits with the rest of SYMI

• Your workspace is what Workspace Mirror synchronizes to an enrolled computer, if you choose to connect one.
• Your workspace is separate from Memory — memory is what SYMI remembers about you and your work; the workspace is the actual files. A memory note might reference a file, but the file itself lives in the workspace.
• Every user’s workspace is isolated from every other user’s. See Security & Isolation for more on that guarantee.

​

Next steps