Manage the knowledge a Cargo workspace holds — upload files (PDF, CSV, text), rename and organize them, and build native or connector-backed libraries that sync from an external source, so agents can retrieve them (RAG). Triggers: "upload this PDF", "add these docs as knowledge", "build a knowledge

Cargo CLI — Content Workspace knowledge management: upload and organize files (PDFs, CSVs, text) and group or sync them into libraries . These are the binary/grouped knowledge resources that ground agent responses (retrieval augmented generation, RAG). 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 ](../cargo ai/SKILL.md). For folders that organize files, use [ cargo workspace management ](../cargo workspace management/SKILL.md) ( 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 ](../cargo workspace management/SKILL.md). 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. Bootstrap Already signed in ( cargo ai whoami returns a workspace)? Skip to the next section. Every command prints JSON to stdout; failures exit non zero with {"errorMessage": "..."} . Anything that creates a run or a batch is async — pass wait until finished or poll the matching get . When the full skill bundle is installed, [ ../cargo/references/prerequisites.md ](../cargo/references/prerequisites.md) adds the CLI version pin, token scopes, and the admin only surface. Discover resources first Files Upload files (PDFs, CSVs, text) so an agent can ground its responses in specific knowledge. The upload response includes the uuid you reference when attaching the file to an agent release (see [ cargo ai ](../cargo ai/SKILL.md)). 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 ](../cargo context/SKILL.md). Libraries A library groups files into one resource an agent can reference. There are two kinds: 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 ](../cargo connection/SKILL.md). Attaching to an agent Files and libraries are knowledge resources — they do nothing until attached to an agent via that agent's draft release resources array, then deployed. That wiring lives in [ cargo ai ](../cargo ai/SKILL.md) ( ai release update draft resources … → ai release deploy draft ). See references/examples/files.md for the upload → attach → deploy sequence. Help Every command supports help :

cargo-content