Bring your own harness
Any agent framework becomes a HUD harness by subclassingAgent and implementing __call__. Open the capabilities you need off run.client, do your work, and write the answer to run.trace.content:
harness.py
Wrap an existing framework: browser-use on cdp
The bundled BrowserUseAgent is exactly this adapter — browser-use driving the cdp (browser) capability:
run.py
ssh, mcp, rfb, robot).
Run on your own infra
The other integration seam is placement: a provider is any callable that takes the task row being placed and yields a connectableRuntime. Your
cluster, a sandbox vendor, or a per-row GPU policy plugs in without touching
the engine:
LocalRuntime, Runtime(url), HUDRuntime).
Any OpenAI-compatible endpoint
OpenAIChatAgent speaks the OpenAI Chat Completions API, so vLLM servers, local models, and hosted checkpoints all work — point base_url at the server:
run.py
Serve an agent over A2A
TheChat runner is protocol-agnostic — an A2A endpoint is a thin adapter that translates requests into chat.send() calls:
cookbooks/a2a-chat/server.py for a complete A2A reference server (per-context sessions, agent card, citations transport) built on a2a-sdk.