📣
TiDB Cloud Premium is now in public preview. Unlimited growth, instant elasticity, advanced security for enterprise workloads. Try it out →

Manage TiDB Cloud Filesystem Resources



TiDB Cloud Filesystem is a serverless distributed file system designed for AI agents and automation workloads. It provides a persistent, shareable file namespace that remains available independently of the local machine, sandbox, or CI runner that accesses it.

You can access files directly through TiDB Cloud CLI commands or mount a Filesystem into a supported environment and work with it like a local file system. This makes it useful for preserving agent state, sharing files across isolated environments, handing off CI artifacts, and maintaining reusable workspaces.

This document describes how to use ti fs commands to create, inspect, select, and delete Filesystem resources.

Prerequisites

Create a Filesystem

Create a Filesystem and save the returned ID and one-time owner token in a file that is not world-readable. The --wait flag tells the CLI to poll until data-plane access is ready before returning:

umask 077 ti fs create-file-system \ --display-name agent-workspace \ --label environment=development \ --wait > ./filesystem.json export TI_FS_FILE_SYSTEM_ID="$(jq -r '.file_system_id' ./filesystem.json)" export TI_FS_TOKEN="$(jq -r '.fs_token' ./filesystem.json)"

List and inspect Filesystems

List the Filesystems available in the effective region:

ti fs list-file-systems --output text

Read authoritative metadata for one Filesystem:

ti fs describe-file-system --file-system-id "<file-system-id>"

If you have access to more than one Filesystem, pass --file-system-id explicitly or set the TI_FS_FILE_SYSTEM_ID environment variable. The CLI does not automatically select a Filesystem for you.

Check access

Verify resource selection, endpoint resolution, credentials, and companion access:

ti fs check-file-system --file-system-id "<file-system-id>"

Delete a Filesystem

Delete a Filesystem by explicit ID:

ti fs delete-file-system --file-system-id "<file-system-id>"

Filesystem deletion is asynchronous. After the service accepts the request, the CLI reports the Filesystem status as deleting and removes the matching local credential. This output does not mean that remote deletion has finished.

What's next

Was this page helpful?