Verify the Sandbox Inference Route

Verify inference through the same inference.local path that the agent uses inside the sandbox. Reading the active route confirms configuration, but it does not authenticate a model request.

Confirm the Configured Route

Read the live gateway route first.

$
nemohermes inference get

Confirm that the provider and model match the route you intended to configure.

Check Sandbox Inference Health

Run the named sandbox status command.

$
nemohermes <name> status

The Inference row checks the sandbox’s inference.local path and reports the provider, model, and endpoint with the rest of the sandbox state. This path includes the OpenShell proxy and its authentication rewrite.

Understand Post-Ready Checks

For local Ollama and vLLM, onboarding performs an additional check after the sandbox becomes ready. It requests https://inference.local/v1/models from inside the sandbox and accepts only a 2xx response. When this check fails, onboarding reports the endpoint and recovery steps before the first agent prompt.

NVIDIA NIM and other compatible endpoints receive their provider validation during onboarding but do not receive this post-ready sandbox-route check. For those routes, use the status command and a short agent request after onboarding.

Send a Short Agent Request

Connect to the sandbox and send a short request before starting long-running work. A successful response proves that the configured model can serve an agent request through the OpenShell route.

If status is healthy but a tool action returns JSON as normal assistant text, troubleshoot structured tool calling instead of the network route.

Related Topics

• View the Active Inference Route to inspect configuration without sending an inference request.
• Understand Provider Validation for the checks that run before sandbox creation.