A task preview runs one task revision as a short-lived App for inspection. It is not your production App and does not inherit that App's secrets, volumes or network identity. Its URL is public to anyone who knows it: do not put confidential data in a preview. You need task visibility and app.preview permission.
Prepare a stateless blueprint
An App blueprint is a project-scoped JSON specification for units, not a deployed App. The built-in minimal example declares a public HTTP runner without environment or volume requirements:
rp app blueprint example > blueprint.json
rp app blueprint validate --file blueprint.json
rp app blueprint create website --file blueprint.json --default
Inspect the file and adapt its Containerfile and port to your project before storing it. Use --default only if the project has no different default; otherwise omit it and name this blueprint explicitly when previewing. A blueprint must declare version 1 and at least one unit; a public unit must be a runner with an HTTP port. Validation does not create an App or allocate resources. rp app blueprint example --full adds inputs unsuitable for the current stateless preview workflow. Changing a stored blueprint replaces its specification; it does not silently rebuild existing previews.
Launch and inspect
rp task preview <number>
rp app logs task-<number> --tail 100
rp task preview <number> --update
rp task preview <number> --stop
Without a project default, supply --blueprint <name> when previewing. The preview records an exact task SHA and blueprint snapshot. Repeating the command returns a matching running preview; when either input changes, inspect the mismatch and use --update only if you intend to replace the old runtime. Build/deployment progress is separate from container logs, which may contain secrets. Previews with required environment values or volumes are refused rather than supplied empty values. A preview expires; use it for feedback, not durable hosting. Apps and deployments explains the production boundary.
The App CLI reference covers blueprint and runtime commands.