Administer a Cargo workspace and talk back to the Cargo team — invite and manage members, mint and rotate API tokens, organize plays, tools, and agents into folders, inspect roles, upload batch input files, and file reports. Triggers: "invite my teammate", "create an API token for CI", "who has acce

Cargo CLI — Workspace Workspace administration: managing users, API tokens, folders, roles, workspace level files, and submitting reports to workspace management. See references/response shapes.md for full JSON response structures. See references/troubleshooting.md for common errors and how to fix them. See references/examples/users.md for user invite and management examples. See references/examples/tokens.md for API token creation and rotation examples. See references/examples/folders.md for organizing resources into folders. See references/examples/reports.md for examples of submitting workspace management reports. See references/examples/sessions.md for session tracking — the Cargo installer scaffolds the Claude Code SessionStart + Stop + SessionEnd hooks automatically. 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 . Admin only: user, role, and token writes require a token with admin access on the workspace. Folder writes and report create work with non admin tokens. 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 Quick reference Current user and workspace Users Roles Roles define what users can do in the workspace. Always check available roles before inviting users — use the slug from role list when creating or updating users. API tokens Each token has a human readable name and a permissions field. Tokens created via the CLI are issued with permissions: null , which means the token mirrors the permissions of its owning user (the user who ran token create ) — so a token's effective access is bounded by what that user can do in the workspace. Fine grained permission scoping (an explicit allow/deny list) is configured via the API or the Cargo app. Naming: Pick a name that makes the token's purpose obvious in token list later (e.g. "GitHub Actions — production" , "Local dev — alice" , "Zapier integration" ). The name is the only way to tell tokens apart in the listing. Security: Token values are only shown once at creation. Store them in a secrets manager (e.g. GitHub Secrets, AWS Secrets Manager). Folders Folders organize resources (plays, tools, agents) in the Cargo app. Reports Submit a report to workspace management. Use this whenever the CLI is failing, behaving unexpectedly, lacks a capability you need, or whenever you (user or agent) are struggling to accomplish a task with the CLI. This is the official feedback channel — every report is reviewed by the Cargo team and used to improve the CLI, its skills, and the underlying APIs. When to send a report (non exhaustive): A command exits non zero with an errorMessage you cannot resolve from help or references/troubleshooting.md . The CLI is being misused or the syntax is unclear (e.g. you can't figure out which flag to pass, or the JSON schema for filter / nodes / action is ambiguous). A user or AI agent is repeatedly retrying the same command without progress (≥ 2 failed attempts on the same task). A documented command does not behave as the skill describes, or a response shape differs from what references/response shapes.md documents. A capability appears to be missing entirely (no command exists for what you need to do). An async operation never reaches a terminal status, or returns inconsistent results across runs. What to put in the report: title : one line summary of the problem (e.g. "batch create fails with 'playNotCompatible' on tool workflow" ). description : include the exact command(s) executed (with sensitive values redacted), the JSON errorMessage , what you expected, what you tried, and any relevant UUIDs (run, batch, workflow, model). The more context you provide, the faster it can be triaged. Do not silently give up on a failing CLI task. Send a report. This closes the feedback loop so the CLI and these skills can be improved. Sessions Record a Claude Code session in workspace management.sessions . One row per (workspaceUuid, sessionId) . Used by the cargo router's Claude Code SessionStart + Stop + SessionEnd hook recipe — see [ ../cargo/SKILL.md ](../cargo/SKILL.md) for when to wire them up. session id , title , summary are required on every call. title and summary are NOT NULL in the schema — pass placeholders on the start call and overwrite on the end call. finished stamps finished at = now . Use finished at <iso for an explicit timestamp instead. Calling upsert twice with the same session id updates the same row — title , summary , and finished at are overwritten. Returns the upserted session as JSON. The [Cargo installer](https://github.com/getcargohq/cargo skills staying current) wires SessionStart + Stop + SessionEnd hooks that call this command automatically: SessionStart writes a placeholder, the per turn Stop hook checkpoints the row (no finished ), and SessionEnd writes the transcript driven AI summary with finished — see [ references/examples/sessions.md ](references/examples/sessions.md). Workspace files Workspace files are CSVs or other data files uploaded for use in batch runs. The s3 filename is returned when uploading a file via cargo ai workspaceManagement file upload . See the cargo orchestration skill's references/examples/tools.md for the full file upload and batch run workflow. Help Every command supports help :

cargo-workspace-management