Cargo CLI — Content

New top-level domain (CLI ≥ 1.0.19). Files and libraries moved out of the

ai

domain into the

content

domain —

cargo-ai content file …

and

cargo-ai content library …

. The old

cargo-ai ai file …

commands no longer exist; an

unknown command

error means you're on the old path.

For attaching a file or library to an agent (via the release

resources

array), use

cargo-ai

. For folders that organize files, use

cargo-workspace-management

(

cargo-ai workspaceManagement folder …

). For batch-run input files (CSVs uploaded to drive a batch), that's a different surface —

cargo-ai workspaceManagement file upload

— documented in

cargo-workspace-management

.

See

references/examples/files.md

for end-to-end file, library, and attach-to-agent examples. See

references/response-shapes.md

for full JSON response structures. See

references/troubleshooting.md

for common errors and how to fix them.

Prerequisites

../cargo/references/prerequisites.md

--oauth

--token

cargo-ai whoami

Discover resources first

cargo-ai content file list                 # all uploaded files (uuid, name, contentType, size)
cargo-ai content library list              # knowledge libraries (native or connector-backed)

Files

uuid

cargo-ai

# List all files
cargo-ai content file list

# Get a single file
cargo-ai content file get <file-uuid>

# Upload a file (optionally straight into a folder)
cargo-ai content file upload --file-path ./knowledge-base.pdf
cargo-ai content file upload --file-path ./knowledge-base.pdf --folder-uuid <folder-uuid>

# Update a file's name or folder
cargo-ai content file update --uuid <file-uuid> --name "Q1 Research Notes"
cargo-ai content file update --uuid <file-uuid> --folder-uuid <folder-uuid>

# Remove a file
cargo-ai content file remove <file-uuid>

Reading content files from the context sandbox. Uploaded content files are also available read-only under

.files/

in the context runtime sandbox, so a command run there can consume them — e.g.

cargo-ai context runtime execute --command ls --args '["-1",".files"]'

. The directory sits outside the committed context tree (never pushed, not writable); to add or change files use

content file

here. See

cargo-context

.

Libraries

• native

  — workspace-managed collections of uploaded files.

• connector

  — synced from an external source (e.g. a help center or knowledge base) through an unstructured-data extractor (

  --extractor-slug

  ). Get the

  connectorUuid

  from

  cargo-connection

  .

# List libraries (filter by kind or connector)
cargo-ai content library list
cargo-ai content library list --kind native
cargo-ai content library list --kind connector --connector-uuid <connector-uuid>

# Get a single library
cargo-ai content library get <library-uuid>

# Create a connector-backed library
cargo-ai content library create \
  --name "Help Center" \
  --connector-uuid <connector-uuid> \
  --extractor-slug <extractor-slug> \
  --folder-uuid <folder-uuid> \
  --config '{}'

# Update / remove
cargo-ai content library update --uuid <library-uuid> --name "Updated Name"
cargo-ai content library remove <library-uuid>

Attaching to an agent

resources

cargo-ai

ai release update-draft --resources …

ai release deploy-draft

references/examples/files.md

Help

--help

cargo-ai content file upload --help
cargo-ai content library create --help