deploy command creates a new agent deployment or updates an existing one. It builds a deployment manifest with the provided parameters and monitors the deployment status until the agent is ready.
If the agent name already exists, you’ll be prompted to confirm the update unless the --force flag is used.
This command will wait for the active deployment / revision to enter a ready state before returning. If the deployment fails, the command will exit with an error with more information.
Usage
Unique string identifier for the agent deployment. Must not contain spaces.
URL of the Docker image to deploy. Must be a valid Docker image URL. For
example:
docker.io/my-repo/my-image:latest.Name of the image pull secret to use for accessing private repositories. The
secret must be previously created using the
pipecat cloud secrets image-pull-secret command.Organization to deploy the agent to. If not provided, uses the current
organization from your configuration.
Name of the secret set to use for the deployment. The secret set must exist in
the specified organization.
Minimum number of agent instances to keep warm at all times. Default is 0,
which means the agent will scale down to zero when not in use. Setting this to
1 or higher avoids cold starts.
Maximum number of allowed agent instances. Must be between 1 and 50. If you
need more agents, please contact us at help@daily.co or via
Discord.
Enable Krisp noise cancellation for this deployed agent. In addition, you also
need to enable the
KrispFilter() for your transport. See the Krisp Noise
Cancellation guide
for more information.Enable managed API keys
for this deployed agent.
The agent profile to use for resource allocation. Valid values are:
agent-1x, agent-2x, agent-3x.See Agent Profiles for more information.Region where the agent will be deployed. If not specified, defaults to
us-west. Choose a region close to your users for optimal latency.Force deployment and skip confirmation prompts. Use with caution.
Examples
Deploy a new agent:Configuration File (pcc-deploy.toml)
Thedeploy command supports a configuration file for repeatable deployments. Create a pcc-deploy.toml file in your project root to define deployment settings that can be shared across your team and version controlled.
File Location
Placepcc-deploy.toml in the same directory where you run the pipecat cloud deploy command. The CLI will automatically detect and use this file.
Precedence
Values are applied with the following order of precedence:- CLI arguments (highest priority)
pcc-deploy.tomlvalues- Default values (lowest priority)
Configuration Options
Required Fields
Name of the agent to deploy. Must start with a lowercase letter or number, can
include hyphens, and must end with a lowercase letter or number.
Docker image URL with tag.
Optional Fields
Region where the agent will be deployed. Defaults to
us-west if not
specified.Name of the secret set to use for environment variables. The secret set must
exist in the same region as the agent.
Name of the image pull secret for private registries. The image pull secret must exist in the same region as the agent.
Agent profile for resource allocation. Valid values:
agent-1x, agent-2x, agent-3x.Deprecated: Enable legacy Krisp noise cancellation. Use
krisp_viva instead.Enable managed API keys for this deployment.
Scaling Configuration
Define auto-scaling behavior in a[scaling] section:
Minimum number of agent instances to keep warm. Setting to 0 allows scaling to zero but may result in cold starts.
Maximum number of agent instances allowed.
Krisp VIVA Configuration
Configure Krisp VIVA noise cancellation in a[krisp_viva] section:
Krisp VIVA audio filter model. Valid values:
tel (telephony, up to 16kHz) or pro (WebRTC, up to 32kHz). Omit or set to null to disable.Complete Example
Using the Configuration File
Once you have apcc-deploy.toml file, simply run: