Agent Harnesses | NVIDIA Dynamo Documentation

Dynamo exposes v1/chat/completions, v1/responses, and v1/messages, so any agent that uses these APIs can talk to a Dynamo endpoint even if it is not listed in this guide. This guide focuses on popular agent harnesses that send stable session IDs. Dynamo normalizes these IDs for tracing and other explicitly configured consumers.

Start a local agent endpoint

To locally test these out, we have a small script that runs an SGLang-backed zai-org/GLM-4.7-Flash endpoint. This script starts a TP2 instance on port 8000 and enables request tracing for replay and visualization. By default traces are saved in /tmp/dynamo-request-trace-$(date +%Y%m%d-%H%M%S)

To start it, run:

$ bash examples/backends/sglang/launch/agg_agent.sh

Configure a harness

Codex

Pi

Claude Code

OpenCode

OpenClaw

Hermes Agent

Codex uses the Responses API. Add a local provider in ~/.codex/config.toml:

1 [model_providers.dynamo]
2 name = "dynamo"
3 base_url = "http://localhost:8000/v1"
4 wire_api = "responses"

$ # replace -m <model> with your model
$ codex -m zai-org/GLM-4.7-Flash -c model_provider=dynamo

Codex sends a session-id header that Dynamo maps to session_id.