Skip to main content
An environment is what the agent sees and acts on, one step at a time: look at the screen, reason, act. An agent gets its environments from its environments list, where each entry is either a catalog name or an inline environment object. At least one is required, with at most one per kind. The Browser is the environment H hosts today, and both the browser and the desktop can run on your own machine with local control. Cloud desktops for Mac, Windows, and Linux are in What’s next.

Toolbox

Attaching an environment equips the agent with a toolbox: the actions it can take on that surface, along with built-in guidance on how to use them. The Browser, for example, contributes web actions such as navigate, click, type, scroll, and read. The set of actions is fixed per environment, so you cannot add or remove individual ones. To shape how the agent uses them, set the agent’s instructions or attach your own skills, which load on demand on top of the built-in guidance.

Built-in environments

H ships browsers in the catalog. Browse them below, or list them with GET /api/v2/environments:

Create your own

Most agents define an environment inline in their environments list. Create a catalog environment instead when you want to reuse one across several agents, then reference it by id:

Endpoints

The list is paginated (page, size) and returns an items / page / total envelope; sort it with sort=created_at, prefixed with - for descending.