File storage

Where xpander keeps agent workspaces, uploads and generated files, and how agents reach your S3 buckets.

Files	Where they live
Agent workspaces: a session’s code, downloads and outputs	Claude Code, Codex and OpenCode agents: fleet volumes on an XFS StorageClass with prjquota, with a 20 GiB limit per agent by default (a ceiling, not reserved space). Agents whose harness is xpander and that use a workspace: a 5 GiB volume each
Uploads, attachments, generated files, live-surface assets	xpander’s asset store on xpander cloud and Hybrid. Supabase Storage on an in-cluster volume on Air-Gapped, which signs Storage URLs instead of using xpander’s CDN
Files in your own S3 buckets	Your AWS account, through the Amazon S3 skill

Workspace volumes

Each agent is a directory on a fleet volume, and every turn runs in its own sandbox against it. The fleet needs an XFS StorageClass with project quotas: set fleet.storage.createClass: true, or name an existing one in fleet.storage.className. Without it, the fleet refuses to start rather than run unbounded. Sizing: Sizing and requirements.

The Computer view in xpander Chat browses the workspace. Credential stores such as .aws, .ssh and .kube never appear in it. See Agent workspace.

Object storage

A self-hosted install needs 48 GiB of volumes for the chart’s stores, plus 500 GiB per executor for the fleet volume, plus 5 GiB for each agent whose harness is xpander and that uses a workspace. On Air-Gapped, Supabase Storage keeps objects on its own in-cluster volume (supabase.storage.persistence, 50 GiB by default):

supabase:
  storage:
    persistence:
      size: 100Gi
      storageClass: gp3
    publicUrl: https://<supabase host>

It runs one replica with no S3 backend, so back the volume up with your snapshot policy. A sealed VPC still needs the S3 gateway endpoint, for ECR image pulls.

S3 as a skill

The Amazon S3 skill is served by the AWS Operator in your cluster. The operator assumes a per-skill IAM role and signs each call, so no bucket credential ever reaches an agent. See IAM best practices and Amazon S3.

Next steps

Size the executor fleet

Workspace sizing

Design IAM roles for AWS skills

Per-skill roles