Update to FastAPI Cloud

{
  "description": "Manage custom domains for FastAPI Cloud apps. Use when listing or inspecting domains, adding a hostname, choosing standard or zero-downtime DNS setup, checking verification or TLS progress, restarting failed setup, or removing a custom domain.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 221
    }
  ],
  "name": "fastapicloud-domains",
  "skill_md_contents": "---\nname: fastapicloud-domains\ndescription: \"Manage custom domains for FastAPI Cloud apps. Use when listing or inspecting domains, adding a hostname, choosing standard or zero-downtime DNS setup, checking verification or TLS progress, restarting failed setup, or removing a custom domain.\"\n---\n\n# FastAPI Cloud Domains\n\n## Overview\n\nAdd, inspect, troubleshoot, and remove custom domains for a FastAPI Cloud app. The CLI reports the DNS records the user must configure; it does not change records at the user's DNS provider.\n\n## CLI Baseline\n\nCustom domain commands require FastAPI Cloud CLI `0.25.0` or newer. Start with the command needed for the task:\n\n```bash\nuv run fastapi cloud domains --help\n```\n\nOnly check the version if the `domains` command is missing or incompatible:\n\n```bash\nuv run fastapi cloud --version\n```\n\nIf an update is needed, ask before changing an existing project environment, then update `fastapi[standard]` rather than installing `fastapi-cli` directly:\n\n```bash\nuv add -U \"fastapi[standard]\"\nuv lock --upgrade-package fastapi --upgrade-package fastapi-cloud-cli\n```\n\n## Authentication And App Resolution\n\nDomain management requires a logged-in user session; a deploy token is only for deployments and CI. If authentication fails, report the blocker and ask before starting the JSON device flow:\n\n```bash\nuv run fastapi cloud auth login --no-open --json\nuv run fastapi cloud auth wait --device-code DEVICE_CODE --interval 5 --timeout 300 --json\n```\n\nUse an explicit `--app-id APP_ID` when the user provides one. Otherwise use the app linked to the current directory. Resolve an uncertain target with read commands before making changes:\n\n```bash\nuv run fastapi cloud apps get --json\nuv run fastapi cloud domains list --app-id APP_ID --json\n```\n\nUse `--json` whenever supported. JSON mode is non-interactive, so provide every required domain, setup mode, and confirmation flag explicitly.\n\n## Inspect Domains\n\nList an app's custom domains before selecting one:\n\n```bash\nuv run fastapi cloud domains list --app-id APP_ID --json\n```\n\nInspect one domain by hostname or domain ID:\n\n```bash\nuv run fastapi cloud domains get DOMAIN --app-id APP_ID --json\n```\n\n`domains get` reports setup status, the DNS records currently required, and the live HTTPS URL after setup succeeds. In JSON mode, `DOMAIN` is required. Use the exact record type, name, and value returned by the CLI; do not infer DNS records from other apps or domains.\n\n## Add A Domain\n\nFirst determine whether the hostname is new or already serves production traffic. If this is unclear, ask—the choice changes the DNS workflow.\n\nFor a new or unused hostname, use standard setup:\n\n```bash\nuv run fastapi cloud domains add DOMAIN --app-id APP_ID --standard --json\n```\n\nFor an already-live hostname, use zero-downtime setup:\n\n```bash\nuv run fastapi cloud domains add DOMAIN --app-id APP_ID --zero-downtime --json\n```\n\n`--standard` and `--zero-downtime` are mutually exclusive. JSON mode requires `DOMAIN` and one setup mode.\n\n- Standard setup returns the records used to verify ownership, issue TLS, and route traffic.\n- Zero-downtime setup proceeds in phases: prove ownership, secure the domain, then switch traffic. Only configure the records currently shown by `domains get`; later records unlock as verification advances.\n\nAfter the user updates DNS, check progress with:\n\n```bash\nuv run fastapi cloud domains get DOMAIN --app-id APP_ID --json\n```\n\nFastAPI Cloud rechecks pending or mismatched records automatically. Do not restart setup merely because DNS is still propagating.\n\n## Restart Failed Setup\n\nRestart only after `domains get` reports a failed setup and the returned DNS records have been checked or corrected:\n\n```bash\nuv run fastapi cloud domains restart DOMAIN --app-id APP_ID --json\nuv run fastapi cloud domains get DOMAIN --app-id APP_ID --json\n```\n\nIn interactive mode, omitting `DOMAIN` offers only failed domains. In JSON mode, `DOMAIN` is required.\n\n## Remove A Domain\n\nInspect the exact domain first and explain the effect. Removal deletes FastAPI Cloud's resources for the domain but does not change DNS records at the provider.\n\n```bash\nuv run fastapi cloud domains get DOMAIN --app-id APP_ID --json\nuv run fastapi cloud domains remove DOMAIN --app-id APP_ID --yes --json\n```\n\nOnly remove a domain when the user explicitly asks. JSON mode requires both `DOMAIN` and `--yes`. After removal, remind the user to review stale DNS records at their provider; do not claim those records were deleted.\n\n## Response\n\nReport the app and hostname affected, the resulting setup status, and the next required DNS action. For setup in progress, include only the currently required records and the next `domains get` command. Never claim a domain is live until the CLI reports successful setup.\n"
}