Skip to content

docs(pipecat-cloud): document that min-agents changes apply asynchronously (T-3351) #1089

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jamsea wants to merge 4 commits into
base: main
Choose a base branch
from
+9 −1
Open

docs(pipecat-cloud): document that min-agents changes apply asynchronously (T-3351) #1089

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
20cf3bc
docs(pipecat-cloud): document that min-agents changes apply asynchron…
jamsea Aug 13, 2026
f088fba
docs(pipecat-cloud): trim min-agents runtime note to a single tip
jamsea Aug 13, 2026
6fdf28f
Potential fix for pull request finding
jamsea Aug 13, 2026
8db5ab1
Update min-agents recommendation timing in documentation
jamsea Aug 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion pipecat-cloud/guides/capacity-planning.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,11 +71,19 @@ To determine the optimal reserved instance count for your deployment, consider:
apps, consider a waiting UX or message.
</Tip>

<Tip>
For a known busy period, raise `min-agents` **3-5 minutes** before your traffic
starts, not seconds. A `min-agents` change is applied asynchronously, so new
instances still need time to become available after the change is accepted.
See [Cold-starts](../fundamentals/scaling#cold-starts) for what makes a
scale-up slower.
</Tip>
Comment thread
jamsea marked this conversation as resolved.

## Cost-Efficient Scaling Strategies

- **Development/Testing**: Use `min-agents: 0` to minimize costs during development
- **Production Voice AI**: Set `min-agents` to cover your baseline traffic to avoid cold starts
- **Time-Based Scaling**: Consider modifying your reserved count for known high-traffic periods
- **Time-Based Scaling**: Consider modifying your reserved count for known high-traffic periods. Make the change ahead of the traffic, not as it starts.
- **Cap session duration**: Use [`--max-session-duration`](/api-reference/cli/cloud/deploy#param-max-session-duration) as a safety net against runaway sessions. If your application's calls are meant to be short, setting a tight cap (e.g. 120s for a 60s use case) prevents a buggy bot from racking up hours of charges.
- **Monitoring**: Regularly review your warm capacity utilization to optimize your configuration
<Info>
Expand Down
Loading