Cargo Hosting

If you're deploying Vite apps or edge workers to Cargo's hosted platform, this wraps the full lifecycle: scaffold a local project from templates, create the slot with a globally unique slug, upload and build your source in Cargo's sandbox, then promote a deployment to go live on *.cargo.app. The two-step deploy-then-promote pattern gives you control over what's actually serving. Apps get wired to your workspace's API with useCargoApi hooks, workers auto-generate OpenAPI specs and Swagger docs. Worth noting that builds run async, so you'll poll deployment status before promoting, and hosting charges workspace credits monthly per resource.

skills.sh installs: 11K
GitHub stars: 22
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add getcargohq/cargo-skills --skill cargo-hosting --agent claude-code

Installs into .claude/skills of the current project.

Files

Cargo CLI — Hosting

Cargo Hosting runs two kinds of workspace-scoped resources, plus the deployments that ship them:

App — a static front end (a Vite single-page app by default; Astro, Gatsby, Create React App, Parcel and Webpack are detected too, and Next.js, SvelteKit or Nuxt work through their own build script, see App builds) served on its own subdomain (see URLs). The templates are built on @cargo-ai/app-sdk (Vite + refine + shadcn primitives, with getCargoEnv() / useCargoApi() wired to the workspace).
Worker — a serverless HTTP handler that runs on the edge (fetch(request, env)), built on @cargo-ai/worker-sdk (auto OpenAPI 3.1 spec at /openapi.json, Swagger UI at /docs).
Deployment — one build+upload of a local source directory to an app or worker. A deployment is not live until it's promoted.

For organizing apps/workers into folders, use cargo-workspace-management (folder …). The --folder-uuid flags here consume those folder UUIDs.

SKILL.md on GitHub