executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
inference-servingServe and consume Dexbotic VLA/VLM policies through the legacy or v1 HTTP APIs and the BasePolicy contract.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this route for policy wrappers, HTTP server/client contracts, action chunks, reset semantics, capability discovery, and optional DM0 realtime serving. Read HTTP and policy contract before wiring a client and troubleshooting when requests fail. Route benchmark setup and hardware bridges to evaluation-deployment.
GET /health, then GET /v1/capabilities; do not guess whether state is required or whether actions are absolute/relative.use_delta from the declared action mode.sampling.num_steps, cfg_scale, and optional seed; verify the action chunk shape and units before passing actions to a robot or simulator./v1/reset at episode boundaries for stateful policies such as MemVLA. Treat a reset failure as a session boundary problem, not a model-quality result./process_frame route only when the consumer requires multipart compatibility.No server, checkpoint download, physical control loop, or Triton weight conversion is run by the bundled smoke helper unless explicitly requested with a reachable local URL.