Daytona Sdk And Client

Engineer initializes the Daytona client and hardcodes the API key string in the agent source so 'it just works' in CI.

Load the Daytona API key from an environment variable / secret manager at runtime; never commit it to source. Scope the key to the minimum org permissions the agent needs and rotate on exposure. [REQUIRES-VERIFICATION] for the exact env var name the SDK reads.

Agent constructs a brand-new Daytona client object on every single SDK call inside a tight loop.

Construct one configured client and reuse it across calls; repeated construction wastes connection setup and may re-auth each time. Treat the client as a long-lived, thread-safe handle if the SDK documents it as such — otherwise pool per worker. [REQUIRES-VERIFICATION] for the client's documented t…

A code-exec call returns a non-zero exit code from the user's program, while a separate call raises an SDK-level exception (e.g. sandbox not found).

Distinguish the two failure planes: a non-zero exit code is the user program's result (inspect stdout/stderr, do not retry the platform), whereas an SDK/transport exception is a platform-layer failure (sandbox gone, auth, network) that may warrant restart or backoff. Branch on which plane failed be…