Update to FastAPI Cloud

{
  "description": "Inspect FastAPI Cloud logs. Use when the user asks for recent logs, the latest or last log timestamp, runtime log lines, build logs for a deployment, whether an app has emitted logs, or a quick app log/health check.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 193
    }
  ],
  "name": "fastapicloud-logs",
  "skill_md_contents": "---\nname: fastapicloud-logs\ndescription: \"Inspect FastAPI Cloud logs. Use when the user asks for recent logs, the latest or last log timestamp, runtime log lines, build logs for a deployment, whether an app has emitted logs, or a quick app log/health check.\"\n---\n\n# FastAPI Cloud Logs\n\n## Overview\n\nInspect FastAPI Cloud logs with the narrowest read-only command that answers the user. Prefer direct log retrieval over broad deployment debugging unless the log output points to a failure that needs deeper triage.\n\n## Command Baseline\n\nConfirm log flags only when needed:\n\n```bash\nuv run fastapi cloud logs --help\n```\n\nUse `uv run fastapi cloud apps get --json` only when resolving the linked current directory. Use `--json` whenever the command supports it.\n\n## App Resolution\n\nResolve the app only as far as needed:\n\n1. Use an explicit app ID, app slug, path, or deployment ID from the user.\n2. Use the linked current directory with `uv run fastapi cloud apps get --json`.\n3. Use `--app-id APP_ID` when the directory is not linked but an app ID is known.\n4. List teams and apps only when the user did not provide an app and the local link cannot resolve one.\n\nDo not create apps, link directories, deploy, or mutate environment variables while answering a log request unless the user explicitly asks.\n\n## Runtime Logs\n\nFor recent runtime logs:\n\n```bash\nuv run fastapi cloud logs . --no-follow --tail 100 --since 30m --json\nuv run fastapi cloud logs --app-id APP_ID --no-follow --tail 100 --since 30m --json\n```\n\nFor the latest log timestamp, try the narrowest command first:\n\n```bash\nuv run fastapi cloud logs . --no-follow --tail 1 --json\nuv run fastapi cloud logs --app-id APP_ID --no-follow --tail 1 --json\n```\n\nIf the command returns no lines or requires a time window, widen with bounded supported ranges such as `30m`, `24h`, `7d`, then `30d`. Do not use very large ranges such as `365d`; report the widest window checked when no logs are found.\n\n## Build Logs\n\nWhen the user asks for build logs or names a deployment:\n\n```bash\nuv run fastapi cloud deployments list --app-id APP_ID --json\nuv run fastapi cloud deployments build-logs DEPLOYMENT_ID --no-follow --json\n```\n\nIf no deployment ID is provided, use the newest deployment from `deployments list`.\n\n### Build Failure Guidance\n\nFastAPI Cloud CLI `0.26.0` or newer includes backend failure guidance when available. In `build-logs --no-follow --json`, inspect `data.failed` and `data.failure` as well as `data.logs`. A non-null `failure` contains `error_code`, `error_title`, `error_message`, and `error_hint`. Surface the backend's title, message, and any non-empty hint; use the error code when it helps identify the failure.\n\nBuild-log commands exit with code 1 for a failed build even when stdout contains a valid JSON result. Parse that result before treating the exit as a command or network error. Empty logs do not establish that a build succeeded: failure guidance can remain available after logs expire. If `failure` is null, use the reported failure state and available logs without inventing a diagnosis.\n\nFor deployment status or persisted failure details:\n\n```bash\nuv run fastapi cloud deployments get DEPLOYMENT_ID --app-id APP_ID --json\n```\n\nInspect `data.deployment.status` and `data.deployment.failure`. Build completion alone does not establish that the deployment is healthy.\n\n## Authentication\n\nTreat auth as a blocker, not the main workflow:\n\n- If a read command returns `not_logged_in` or `invalid_token`, stop and tell the user authentication is blocking the log request.\n- Ask before starting the device login flow.\n- After approval, use 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\nSurface only the login URL or user code needed for authorization. Do not print token values, ask the user to paste tokens, or inspect `FASTAPI_CLOUD_TOKEN` unless the user is debugging CI/auth configuration.\n\n## Response\n\nAnswer the concrete log question first: newest timestamp, matching log lines, empty result, or the auth/app-resolution blocker. Include the app name or ID only when it clarifies the evidence, and keep follow-up diagnostics to the next likely command.\n"
}