Skip to main content
The build command provides tools for managing cloud builds on Pipecat Cloud. You can view build logs, check build status, and list recent builds. Cloud builds are typically triggered automatically when you run pipecat cloud deploy without specifying an image. These commands help you monitor and manage those builds.

logs

View logs for a cloud build. Usage:
Arguments:
string
required
The ID of the build to get logs for. You can find build IDs using pipecat cloud build list.
Options:
number
default:"500"
Number of log lines to retrieve. Maximum is 10000.
string
Organization to use. If not provided, uses the current organization from your configuration.

status

Get the current status of a cloud build. Usage:
Arguments:
string
required
The ID of the build to check.
Options:
string
Organization to use. If not provided, uses the current organization from your configuration.
The status command displays detailed build information including:
  • Current status (pending, building, success, failed, timeout)
  • Region, context hash, and Dockerfile path
  • Timestamps for creation, start, and completion
  • Build duration and context/image sizes
  • Error messages (if the build failed)
For a build triggered from a GitHub-linked agent, it also reports the repository, the ref, and the commit the build came from.

list

List recent cloud builds. Usage:
Options:
number
default:"10"
Number of builds to list. Maximum is 100.
string
Filter by build status. Valid values: pending, building, success, failed, timeout.
string
Filter by region.
string
Organization to use. If not provided, uses the current organization from your configuration.
The listing carries a Source column. GitHub-triggered builds show owner/repo@commit; a build from a local context has no commit provenance and shows nothing there.

Examples

List all recent builds:
List only failed builds:
View logs for a specific build:
Check status of a build: