Skip to main content
These pages explain how the SDK is implemented, for people changing it. The rest of the docs teach the API from the outside; this section teaches the code from the inside. Nothing here is needed to build environments or run evals. The mental model is small: an environment declares what exists (capabilities and tasks), a provider brings that environment up somewhere as a server, and a client in your process drives one agent through it over a thin wire protocol. Everything else is a variation on that single loop.

​
Pages

​
The code, at a glance

The SDK splits into two halves that meet at the wire protocol. One half declares and serves an environment; the other places and drives it. A Task row is the only thing that crosses between them at rest, and a TCP control channel is the only thing that connects them at run time. The walkthrough orders these files by the path one rollout takes through them.