feat(sdk,cli): sandbox TTL support

[MDzaja]

Client-side support for the new sandbox TTL (maximum time to live) feature.

What TTL is

A wall-clock deadline after which a sandbox is destroyed regardless of its state (started, stopped, paused, archived). Class-agnostic and orthogonal to the idle-based intervals — no mutual exclusivity, no ephemeral/class gating.

API surface (all SDKs + CLI + MCP)

• ttlMinutes — input-only create parameter (minutes; 0 = disabled). Client-side validated as a non-negative integer. Never stored or returned on the sandbox object.
• expiresAt — read-only field on the sandbox object, mapped from the DTO. Only set when a TTL is configured.
• setTtl(minutes) — re-anchors the deadline from the current time (sliding, so it can extend or shorten the remaining lifetime); 0 disables.
• CLI: daytona sandbox create --ttl <minutes>; MCP: ttlMinutes arg on the create_sandbox tool.

Setter semantics

• The setter returns void and does not mutate local state — the server computes the deadline.
• Read the updated deadline via refreshData() / refresh_data(), which populates expiresAt.

Per-language surface:

SDK	Create param	Read field	Setter
TypeScript	ttlMinutes	sandbox.expiresAt	sandbox.setTtl()
Python (sync + async)	ttl_minutes	sandbox.expires_at	sandbox.set_ttl()
Go	TtlMinutes	Sandbox.ExpiresAt	— (mirrors existing convention: no interval setters)
Java	ttlMinutes	getExpiresAt()	setTtl(int)
Ruby	ttl_minutes	#expires_at	#ttl_minutes=

Generated clients

openapi-specs/api.json synced with the new API surface; all api-client* regenerated (setTtl operation, CreateSandbox.ttlMinutes, Sandbox.expiresAt). Regeneration is byte-stable against the committed spec.

---

Summary by cubic

Add sandbox TTL across SDKs and CLI. Users can set a wall-clock expiration that destroys a sandbox when it elapses; the deadline is exposed as autoDestroyAt.

• New Features

  • API: POST /sandbox/{sandboxIdOrName}/ttl/{ttlMinutes} (setTtl). openapi-specs/api.json updated; all api-client* regenerated.
  • SDKs: Add create param ttlMinutes and read-only autoDestroyAt in sdk-typescript, sdk-python (sync/async), sdk-java, sdk-ruby, sdk-go. Setters: TypeScript sandbox.setTtl(minutes), Python sandbox.set_ttl(minutes) / async_sandbox.set_ttl(minutes), Java sandbox.setTtl(int), Ruby sandbox.ttl_minutes = minutes; Go exposes AutoDestroyAt and accepts TtlMinutes on create.
  • Behavior: 0 disables TTL. Setter re-anchors from now; server computes the deadline. Call refreshData() / refresh_data() / #refresh to read updated autoDestroyAt.
  • Validation: All SDKs and CLI reject negative TTL with clear errors.
  • CLI/MCP: daytona sandbox create --ttl <minutes>; MCP create_sandbox supports ttlMinutes.
  • Docs: SDK docs updated to cover TTL and autoDestroyAt.

• Refactors

  • Rename expiresAt to autoDestroyAt across SDKs, API clients, and docs.
  • Go: refresh now populates AutoDestroyAt; minor cleanup.
  • Java: Sandbox.setTtl validates non-negative input and delegates to the API without mutating local state; Java SDK docs fixed/clarified for TTL and getAutoDestroyAt().

^{Written for commit 340ee6b. Summary will update on new commits.}

[cubic-dev-ai]

All reported issues were addressed across 71 files

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 4 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>