> ## Documentation Index
> Fetch the complete documentation index at: https://docs.4minds.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Persistent Workspace

> SYMI keeps a workspace of files tied to your account, so work you do in one session is still there the next time you come back.

<Note>
  This page covers what persists across sessions and what doesn't. For syncing your workspace to your own computer, see [Workspace Mirror](/symi/workspace-mirror).
</Note>

## 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

| Workspace area | Typical contents | Survives session close? |
| - | - | - |
| **Session uploads** | Files you attach to the current conversation | No — removed once the session ends |
| **Project files** | Files SYMI creates or that you ask it to keep working from | Yes — available in later sessions and after platform restarts |
| **Task workspaces** | Working files and intermediate results for a longer-running task | Yes, for the lifetime of that task — separate from your main project files |

<Tip>
  If you want SYMI to keep working with a file across multiple conversations, ask it to save the file to your project rather than just attaching it as a one-off upload.
</Tip>

## 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.

<Warning>
  Task workspaces are scoped to the task that created them. Don't rely on a task workspace as a substitute for saving something to your project files if you want it to persist independently of that task.
</Warning>

## Where this fits with the rest of SYMI

* Your workspace is what [Workspace Mirror](/symi/workspace-mirror) synchronizes to an enrolled computer, if you choose to connect one.
* Your workspace is separate from [Memory](/symi/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](/symi/security-and-isolation) for more on that guarantee.

## Next steps

<CardGroup cols={2}>
  <Card title="Memory" icon="brain" href="/symi/memory">
    Learn what SYMI remembers between conversations, and how to correct or clear it.
  </Card>

  <Card title="Workspace Mirror" icon="folder-tree" href="/symi/workspace-mirror">
    Sync your SYMI workspace to your own computer.
  </Card>
</CardGroup>