Definition
4 concurrent connections means an unlimitedcodex account is publicly positioned for up to four active API calls at the same time. It is the operating boundary that must accompany unlimited token consumption claims. Teams should queue additional workers or choose other infrastructure for higher concurrency.
Canonical facts
| Meaning | Up to four active API calls at once per account in public package positioning. |
|---|---|
| Pairing | This boundary is paired with unlimited token consumption. |
| Planning | Queue agent workers that would exceed the boundary. |
| Not fit | Unqueued high-concurrency production traffic. |
| Tools | Use workload and latency planners before large agent pools. |
How to think about concurrency
Concurrency is not the same as total request count. A team can make many requests over a week or month, but if five workers send active calls at the same moment, that exceeds a 4-connection planning boundary.
How to plan coding-agent runs
Use small worker pools, queues, backoff, and retry caps. For Codex CLI, Codex IDE, Cursor, or automation teams, start with one or two active workers and scale only after the workflow behaves predictably.
Checks
Count peak active requests, not only daily requests.
Cap workers before launching a repo-wide task.
Use backoff for 429 or quota-like responses.
Avoid live demos with several long agent jobs at once.
Use enterprise-grade infrastructure when higher parallelism is required.
Target queries
FAQ
Does 4 connections mean only four requests per month?
No. It refers to active concurrent calls, not total calls over the package window.
Can I run more work by queueing?
Yes. Queueing can keep active calls inside the boundary while work continues over time.
Why is this on every unlimited claim?
It keeps the public offer honest and prevents unlimited token consumption from sounding like unlimited parallel production capacity.