Cua Cloud Fleets Adds Auto-Expiring TTLs for Agent Sandboxes
- Source
- Cua
- Date
1/ Cua Cloud Fleet resources can now clean themselves up. Set a creation-age TTL on a pool or claim, and Fleet deletes it automatically when the deadline arrives. Useful for CI, eval runs, and temporary agent workloads. Launch a Cloud Fleet today: https://t.co/1qqkbXXZ4o
2/ The same field works at both levels: Pool: ttl_seconds_after_created=86400 Claim: ttl_seconds_after_created=3600 No TTL means no automatic expiry. The pool or claim stays live until you explicitly delete it.
3/ The clock starts at creation and not at last use. Reapplying a named pool does not reset its age. Reconnecting to a named claim keeps its original deadline.
4/ One important boundary: if a pool expires while a claim is still held, Fleet drains the pool. That claim's sandbox is destroyed when released instead of returning to warm capacity. Docs: https://t.co/mQSMecAHE1
- Cua Cloud Fleet pools and claims accept ttl_seconds_after_created (for example 86400 on a pool, 3600 on a claim), after which Fleet deletes them; with no TTL they stay live until explicitly deleted.
- The TTL clock starts at creation, not last use: reapplying a named pool does not reset its age, and reconnecting to a named claim keeps its original deadline.
- If a pool expires while a claim is still held, Fleet drains the pool, and that claim's is destroyed on release instead of returning to warm capacity.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
- eval — A repeatable test for AI quality — a set of tasks plus scoring — used the way software teams use test suites, because model output is too variable to judge by eyeballing.
- sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.
Removes a common source of leaked cloud spend when running many ephemeral sandboxes for CI or .
Checking sign-in…
Loading comments…