Diagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use deploy-dynamo-recipe or dynamo-router-starter before this for normal bring-up.
AGENTS.md instructions for ai-dynamo/dynamo, covering dynamo — agent guide, agent instruction files, skills, improving these instructions and optimization role dispatch.
Agent hints are optional per-request metadata that a harness sends under nvext.agenthints. Dynamo parses these hints in the frontend and passes them to the router and, where supported, backend runtimes.
Agent tracing captures request timing, token counts, worker placement, finish metadata, and replay hashes for eligible LLM requests. Requests with session identity also carry agent context, which lets analysis tools group LLM turns and tool activity into the same run.
NVIDIA Dynamo adds agent-aware serving features without taking ownership of the agent loop: your harness still manages prompts, tools, subagents, and reasoning state, while Dynamo uses metadata attached to each LLM request to correlate work, improve routing and scheduling, manage KV cache behavior, and produce traces…
Agent "thunderagent-program-scheduler" from ai-dynamo/dynamo, covering the problem, the scheduler, scheduler tick, tool-boundary pause/resume semantics and program lifetime.