fused-storagelisted

# Storage & secrets in fused > **Part of the Fused skill set — don't work from it alone.** Fused is `workspace ⊃ > project ⊃ UDF`. If this is a step in building or running a project, load > **`fused-projects`** for the end-to-end model and **`fused-execute`** for running > code over the data. See **`fused-guide`** for the full set. These commands are the **find → load → explore** front of the workflow: locate data, understand its shape, and move bytes in/out — *before* you run code over it with `fused code run`. They operate on the **resolved environment's** storage backend — real S3 on AWS, the local filesystem on the local backend — so the same commands work on either. Pass `--env NAME` (root option, before the group) to pick an environment explicitly. > These used to be MCP tools (`list_files`, `count_files`, `get_file`, > `get_file_schema`, `upload_file`, `get_secret`, `put_secret`, `list_secrets`, > `delete_secret`). The MCP server is gone; the CLI commands below are the > replacement. ## Inspect before you compute The cheapest way to avoid a wasted `code run` is to look first. Typical flow: `files list` → `files count` → `files schema`, then write code against a known schema. ### `fused files list [--bucket B] [--prefix P] [--page-size N]` - **No `--bucket`** → lists buckets. - **With `--bucket`** → lists keys under `--prefix`. The CLI **paginates automatically** and prints every key; `--page-size` only controls the request size. ```sh fused files list