Skip to main content
Author and test an environment with the SDK guide. This page is the platform half, from hud deploy to a running task. A first deployment needs a team API key and two commands:
Create a key under API Keys. After the upload begins, open Environments to follow the build.

​
Environment, build, and template

An environment is the stable platform record. Each deployment creates a build, an immutable version of its source and runnable image. A successful build exposes the environment’s @env.template() definitions as task templates. This separation lets you inspect old builds while new work is building. Runs started during an active build can continue using the previous successful build until the new one is ready.

​
Follow a deployment

The environment page shows an active build on the overview and keeps the full history under Builds. Open a build to read its logs and source. A failed build does not replace the latest successful one.

​
Configure runtime variables

An environment can declare variables that its tasks need, such as credentials for an external service. Open Settings to add them. Values are masked after saving and injected when HUD starts an instance for that environment. The overview separates missing required variables from optional ones. A task cannot run until the variables required by its template are configured.
Compute resources and timeouts belong to the task’s RuntimeConfig, not the environment settings page. This keeps placement requirements attached to the work that needs them.

​
Run a task template

Open Templates after the build succeeds. Select a template, fill its arguments, choose a model, and start a run. HUD creates a job containing one or more traces and opens the job page as soon as the batch is queued. For a reusable suite, create concrete tasks from the template and group them in a taskset. Tasksets are the normal input to a multi-model evaluation.

​
Read the environment page

Public viewers see the overview and templates. Editors see the operational tabs.

​
Share or publish

Share grants another team or member scoped access without making the environment public. Publish makes a private environment publicly discoverable and requires a successful build. Use Public view to preview what other users will see before publishing. The tasks that belong with the environment publish through tasksets.