Ai

Daytona v0.168.0 Expands Sandbox Visibility and Resource Controls

Daytona v0.168.0 Expands Sandbox Visibility and Resource Controls

Daytona v0.168.0 is a focused platform update that improves how teams monitor and manage sandbox environments. This release adds sandbox last-activity timestamps across the API, CLI, dashboard, and SDKs, surfaces per-sandbox resource limits in regional usage views, and introduces runner-side resource limit support. Alongside those additions, it also improves CLI error guidance, fixes preview path handling through the proxy, and resolves a Python SDK error-check issue.

What Changed

The most important addition in v0.168.0 is broader sandbox observability. Daytona now exposes a sandbox last activity timestamp across multiple product surfaces, including the API, CLI, dashboard, and SDKs. For teams operating many ephemeral development environments, this makes it easier to identify stale sandboxes, understand recent usage, and support cleanup or governance workflows.

The dashboard also now shows per-sandbox resource limits inside the region usage overview. That gives administrators a clearer operational picture of how sandbox capacity is allocated and constrained across regions. In the runner layer, Daytona added build resource limits, extending resource control deeper into execution infrastructure rather than leaving visibility only at the UI level.

Outside the headline features, the release includes a small documentation addition with a new robots.txt file, dashboard refactors such as removing suspend-react and restoring client-side pagination for sandboxes, and dependency maintenance updates.

Fixes in This Version

Daytona v0.168.0 also tightens up several rough edges. The CLI now shows a more actionable hint whenever API calls return a 403 Forbidden response, which should make access or permission issues faster to diagnose. The proxy has been fixed to preserve raw encoded preview paths across proxy hops, addressing path-handling problems in preview flows. For Python users, the SDK now fixes an unreachable error check in wait_for_resize and snapshot_complete().

Why It Matters

This is not a flashy release, but it is a meaningful operational one. The combination of last-activity tracking and per-sandbox resource limit visibility makes Daytona more manageable for organizations running large volumes of isolated environments. Those changes support better utilization tracking, stronger governance, and clearer capacity planning.

The usability fixes matter as well. Better 403 guidance in the CLI reduces friction for developers, while the proxy and Python SDK fixes improve reliability in day-to-day workflows. Taken together, v0.168.0 strengthens Daytona’s platform maturity by improving observability, control, and troubleshooting rather than introducing disruptive workflow changes.

Official Source: https://github.com/daytonaio/daytona/releases/tag/v0.168.0