AppDeploy

Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.

Use this when you need to manage a custom domain for an existing app, including adding a hostname, verifying DNS, or deleting it.

Create a one-time pre-authorized browser link so the user can submit a backend secret value outside chat without an extra login step. The returned secret_entry_url should be opened in a new tab. In terminal or CLI clients, present the full raw URL in plain text instead of a markdown link label.

Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.

Delete one or more backend secret names from an existing app. Missing names are ignored.

Use this when the user asks to deploy or publish a website or web app and wants a public URL. If the user plans to provide large resources later (images/PDF/media/fonts), include resource_requirements with stable target_path placeholders so the widget can request exact files and uploads can resolve those paths. For each resource_requirements slot, ensure type resolution via accept and/or target_path extension so widget placeholders map to the right file type. If user-attached files are intended as resources, do not stream them as base64 in files[]; have the user upload them via the widget Resources flow. If the user attaches a file in chat and asks to use it in the app, treat that file as a widget resource: define deploy_app.resource_requirements, reference the target_path placeholder in code, and use the Resources upload flow. Do not encode or inline the attachment as base64 in deploy_app.files[]. When setting resource_requirements.name, keep labels faithful to user wording and do not invent terms. Do not use components names from the template. Every deploy_app call must include non-empty 'model' and 'intent'. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints. After deploy_app starts, keep polling get_app_status every 5 seconds in the same turn until terminal status. Do not hand status polling back to the user. If get_app_status returns QA/e2e/runtime errors, attempt automatic fixes and redeploy up to 3 times before asking the user for guidance.

Use this when deploy_app returns, when checking deployment status, or when the app has errors or is not working as expected. Returns deployment status, e2e test status, QA snapshot, and frontend/backend error logs; treat deployed_and_testing status as non-final, always inspect QA/errors, and call get_e2e_qa_run_details if e2e tests fail.

Use this when you need the base app template and SDK types after selecting an app type and frontend template. Requires calling get_deploy_instructions first.

Use this when you need to list available deployable versions for an existing app. Returns newest-first items with name, version, and timestamp; display the name to users and convert timestamps to local time.

Use this when you need the authoritative @appdeploy/sdk API reference (types and examples) before writing backend persistence code such as counters, CRUD, file uploads, or configuration storage in backend/index.ts.

Use this when you need to list apps owned by the current user. Response also includes a link to the user's web dashboard showing all apps with their details and configurations.

Use this when you need setup guidance or to check the current custom domain status for an app. Returns configured hostnames, DNS instructions, stage proxy targets, fallback IPv4 addresses, and next steps.

Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.

Use this when the user explicitly asks to re-check the deployment status of an app after calling deploy_app, or when the widget is unavailable. Requires the app_id of an existing deployment.

Use this when investigating a failed e2e QA run right after get_app_status reports e2e_tests.status='failed'. Returns the QA transcript, structured results, trace and replay URLs, and debugging keys_prefix.

Use this when the user asks to check for deployment errors, debug issues, or view frontend or backend runtime error logs for a deployed app, or reports that the app is not working as expected. Requires the app_id of an existing deployment; optional parameters may be used to fetch errors newer than a given timestamp.

Poll the lifecycle state of a one-time secret entry link after the user opens the browser page and submits the value.

List backend secret names currently configured for an existing app. Values are never returned.

Attach one or more submitted secret entry ids to an existing app. Reusing a secret name replaces the stored value for that app.

Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.

Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.

Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.

Widget-only helper for ChatGPT web and Claude web. Creates a one-time upload URL for large binary resources (images/PDF/media/fonts) and binds that upload to this session's widget resource channel.