Skip to main content

​
Mental model

Think of the session workspace as the durable file surface for a conversation or task. Clients can:
  • Upload reusable assets before sending a message
  • Write files directly into the session workspace
  • Browse files by path
  • Download file content by path

​
Why the model is session-first

The platform keeps the file contract simple by exposing:
  • Session filesystem paths
  • File metadata
instead of a separate artifact system.

​
Typical flow

  1. Upload a file with POST /v1/files
  2. Reference it from a message part by file_id
  3. Let the runtime read or create workspace files
  4. Browse the resulting workspace with GET /v1/sessions/{session_id}/files

​
Bucket-backed workspaces

When enabled, Dari can mount a customer-approved GCS or S3 session prefix into a scoped subtree of the session workspace. Read Storage Overview for the production access model and cloud setup steps.

​
File changes

File writes are reflected in the session workspace directly. For now, clients should treat the session filesystem as the source of truth and inspect paths in the workspace rather than relying on per-message file diffs.