/gcs/. All operations involve network I/O to the remote object
store. Uses aioboto3 against GCS’s S3-compatible XML API via HMAC keys,
inheriting all S3 VFS capabilities.
For credential setup, see GCS Setup.
Install the extra:
Config
GCSVFS(config) takes a GCSConfig object with the bucket name
and HMAC credentials. Both READ and WRITE modes are supported.
Fields marked secret are redacted in snapshots.
For
write: conditional on this provider, see S3-compatible stores.
VFS.md
The VFS.md an agent reads with GCS mounted at/<path>.
- Rendered
- Raw
mirage-ai contains:
/gcs/ exposes:
/gcs/data/example.json maps to GCS key
data/example.json.
Cache
The GCS VFS usesIndexCacheStore with index_ttl = 600
(10 minutes), same as S3. Directory listings are cached for up to 600
seconds before being refreshed from GCS. This reduces API calls for
repeated directory traversals. A configured index: replaces this lifetime with its own ttl, and the mount’s ttl: caps it.
Integration
What GCS answers through its own API, so fewer files are read. Integration explains each command.Example
Shell Commands
The GCS VFS 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
Use Cases
- AI agents accessing GCS data: Mount GCS buckets for agents to read and process datasets
- Data pipelines: Read and write GCS objects with shell-like commands
- FUSE mounting: Expose GCS buckets through a virtual FUSE mount for external tools