Auree Aubert
4c933393dd
* Migrate file/library docs to the new content domain + register new CLI surfaces The CLI moved workspace files and knowledge libraries out of the `ai` domain into a new top-level `content` domain (`content file`, `content library`), and added inline `ai document`. The old `cargo-ai ai file ...` commands no longer exist. - cargo-ai (2.0.0): migrate every `ai file` reference to `content file`; document `content library` (native vs connector-backed) and `ai document`; rename the Files section and add a command-surface-change callout. - cargo (1.2.0): register the content domain in the recap/table, add a "CLI domains without a dedicated skill yet" table (segmentation, expression, system-of-record, revenue-organization, hosting, user-management), add glossary entries for the content domain and libraries. - cargo-context (1.0.2), cargo-orchestration: fix cross-skill RAG examples. - skills-lint: add the new CLI domains to the known-domain allowlist. * cargo-context/cargo-ai: document content files exposed read-only under .files/ Uploaded `content file` knowledge surfaces in the context runtime sandbox under a read-only `.files/` directory that sits outside the committed context tree, so sandbox commands can consume content uploads without round-tripping them back into the context repo. * Split the content domain into a dedicated cargo-content skill The content CLI domain (files + libraries) was documented inside cargo-ai. Per the repo's one-skill-per-CLI-domain convention, extract it into its own cargo-content capability skill: - New cargo-content/ skill: files + libraries command docs, the moved examples/files.md walkthrough, response shapes, and troubleshooting. - cargo-ai keeps inline documents (ai document) and the attach-to-agent wiring; cross-links cargo-content for files/libraries. - Register cargo-content across the router overview (cargo/SKILL.md table, recap, dependency diagram/rules, counts), glossary, README, and AGENTS.md. - cargo-context documents content files mounted read-only under .files/. - Version bumps: cargo 1.3.0, cargo-ai 2.1.0, cargo-content 1.0.0, cargo-context 1.1.0; CHANGELOG updated. * Drop ai document from cargo-ai; correct content file response shape - Remove the low-value ai document (inline documents) commands from cargo-ai and scrub document references from the router overview, README, glossary, and the cargo-content files.md walkthrough. - Reframe cargo-ai's knowledge section around files & libraries only. - Update the content file list response shape to match the workspace File type: libraryUuid, userUuid, isIndexedInOpenAiVectorStore, externalId, deletedAt, and the native/connector kind union (connectorUuid). --------- Co-authored-by: Claude <noreply@anthropic.com>
1.3 KiB
Content troubleshooting
Common errors in the content domain and how to fix them.
unknown command 'file' / unknown command 'library'
File and library commands moved from the ai domain to the new top-level content domain in CLI ≥ 1.0.19. Use cargo-ai content file … / cargo-ai content library … — the old cargo-ai ai file … path no longer exists. If you still hit this on the new path, bump the CLI: npm install -g @cargo-ai/cli@latest.
fileNotFound
The file UUID does not exist or has been deleted. Run cargo-ai content file list to get the current list.
folderNotFound
The folder UUID passed to --folder-uuid does not exist. Folders are managed by the cargo-workspace-management skill — run cargo-ai workspaceManagement folder list to find valid folder UUIDs, or cargo-ai workspaceManagement folder create --kind file ... to create one.
Upload fails or times out
Large files may take longer to upload. Ensure the file path is correct and the file is not locked by another process.
Library created but the agent doesn't use it
A file or library is inert until it's attached to an agent's deployed release. Add it to the draft release resources array and deploy — see cargo-ai and examples/files.md.