Skip to main content
The Supabase resource mounts a Supabase Storage bucket at some prefix such as /supabase/. All operations involve network I/O to the remote object store. Uses aioboto3 against Supabase’s S3-compatible API. For credential setup, see Supabase Setup.

Config

SupabaseResource(config) takes a SupabaseConfig object with the bucket name, region, and either project_ref (endpoint is auto-built as https://{project_ref}.storage.supabase.co/storage/v1/s3) or an explicit endpoint_url. Both READ and WRITE modes are supported.

Filesystem Layout

The Supabase resource maps object keys to virtual paths under the mount prefix. Supabase “directories” are prefix-based — there are no real directory objects. For example, if bucket my-bucket contains:
Then mounting at /supabase/ exposes:
Path mapping: virtual /supabase/avatars/user-001.png maps to Supabase key avatars/user-001.png.

Cache

The Supabase resource uses IndexCacheStore with index_ttl = 600 (10 minutes). Directory listings are cached for up to 600 seconds before being refreshed from Supabase.

Example

Shell Commands

The Supabase resource supports the full set of shell commands since it operates on real file content (text, binary, JSON, CSV, etc.). Large files benefit from range reads to avoid downloading entire objects.

Read Commands

Text Processing

File Operations

Path Utilities

Compression

Encoding

Data Format Support

Commands with format-specific variants for structured data files: These variants auto-detect the format by extension and convert to tabular text (CSV) for processing.

Use Cases

  • AI agents accessing Supabase data: Mount Supabase buckets for agents to read and process datasets
  • Data pipelines: Read and write Supabase objects with shell-like commands
  • FUSE mounting: Expose Supabase buckets through a virtual FUSE mount for external tools