Files & tools

Drive & computer

Where your files live, and the isolated machine your workspace uses to work on them.

Every workspace has a drive — a plain file tree you can browse, upload to, and download from — and a computer that can actually do something with what’s on it.

The drive

Find it under Files. Upload one file or many; drag whole folders. Organise them however you like.

The drive is where things land:

  • files you upload,
  • files the assistant generates — reports, exports, transformed spreadsheets,
  • attachments that arrive through a chat channel,
  • output from workers and scheduled jobs.

Files belong to the workspace, not to you personally. Anyone with access to the workspace can see them, subject to their role.

The workspace computer

Some jobs need real computation: parsing a 200,000-row CSV, converting a folder of documents, running a calculation over a dataset that’s too big to hold in a conversation.

For those, the workspace has its own machine. It’s an isolated environment — one per workspace — where the assistant and your workers can run code against your files. It starts when it’s needed, stays warm while you’re working, and shuts down when it’s idle.

What that means for you in practice:

  • It’s yours. One workspace’s computer cannot see another workspace’s files. The boundary is the machine itself, not a check in the software.
  • It’s real. The assistant isn’t guessing at what’s in your spreadsheet; it opens it.
  • It’s temporary. Anything the assistant wants to keep, it writes to your drive. Scratch work in the machine’s own temporary space is not preserved between runs.

You don’t manage it. There’s nothing to provision, size or restart.

Working with files

Ask in plain language:

  • “Import q3-leads.csv into Leads.”
  • “Take every PDF in /invoices/2026 and pull out the totals into a table.”
  • “Convert these images to web-sized versions and put them in /exports.”
  • “This spreadsheet has three sheets — turn the second one into a type.”

The assistant tells you what it read, what it skipped and where it wrote the result. Big jobs get handed to a worker so you can carry on with something else.

Size and sanity

  • Very large files are handled by the computer rather than being read into a conversation, so size is a practical limit, not a hard wall.
  • If a file is malformed, you get told which rows or pages failed and why, rather than a silent partial import.
  • Generated files are timestamped so a re-run doesn’t quietly overwrite yesterday’s output.

Next