InferenceManage Inference

Configure Inference Timeouts

View as Markdown

NemoClaw uses separate time budgets for agent requests, local provider validation, sandbox readiness, and recovery. Change the budget that matches the phase that times out.

Choose the Timeout

Use the error location to select the correct setting.

SettingApplies toDefault
NEMOCLAW_AGENT_TIMEOUTOpenClaw per-request inference600 seconds
NEMOCLAW_ONBOARD_VALIDATION_TIMEOUT_SECONDSApplicable OpenAI-compatible provider validation during onboarding, including DeepSeek V4 Pro streaming validationProbe-specific; the standard WSL2 profile uses a 20-second connection and 30-second total floor, while extended NVIDIA validation uses 30 and 300 seconds on WSL2 or 10 and 300 seconds elsewhere
NEMOCLAW_LOCAL_INFERENCE_TIMEOUTOllama, vLLM, NIM, and compatible-endpoint onboarding validation paths that read this setting180 seconds
NEMOCLAW_SANDBOX_READY_TIMEOUTImage build, gateway upload, and in-sandbox boot after creation180 seconds
NEMOCLAW_GATEWAY_RECOVERY_WAIT_SECONDSOpenShell command re-registration after policy application, gateway startup after an intentional OpenClaw stop, and gateway health and OpenShell readiness during managed or provider recovery30, 90, or 120 seconds, depending on the recovery phase

The readiness timeout does not govern inference requests or provider validation.

NEMOCLAW_AGENT_TIMEOUT requires a positive integer; onboarding rejects any other value. NEMOCLAW_ONBOARD_VALIDATION_TIMEOUT_SECONDS accepts positive finite seconds, rounds fractional values up, and caps higher values at 600 seconds. An unset or invalid value preserves the probe defaults. NemoClaw raises each connection or total deadline only when the value exceeds that deadline. NEMOCLAW_LOCAL_INFERENCE_TIMEOUT and NEMOCLAW_SANDBOX_READY_TIMEOUT accept finite, nonnegative seconds, round fractional values, and use their defaults for invalid or negative values. NEMOCLAW_GATEWAY_RECOVERY_WAIT_SECONDS accepts finite, nonnegative seconds and preserves fractional values. A valid value overrides the internal budget for the current recovery phase. An unset, blank, invalid, or negative value uses 30 seconds for OpenClaw gateway health, 90 seconds for Hermes gateway health, and 120 seconds for post-recovery OpenShell readiness when the recovery path does not supply another budget.

Increase the OpenClaw Request Timeout

Deep Agents does not consume the OpenClaw-only NEMOCLAW_AGENT_TIMEOUT setting.

Increase the Provider Validation Timeout

On any platform, increase NEMOCLAW_ONBOARD_VALIDATION_TIMEOUT_SECONDS when an applicable OpenAI-compatible provider validation request times out before the provider replies. NemoClaw automatically prints this recovery advice after WSL2 transport failures.

NEMOCLAW_ONBOARD_VALIDATION_TIMEOUT_SECONDS=360 nemo-deepagents onboard

This setting only raises applicable provider-validation connection and total deadlines, up to 600 seconds. It includes the dedicated DeepSeek V4 Pro streaming validation profile, but it does not extend the separate fixed five-second streaming-event probe. Standard WSL2 validation starts with a 20-second connection and 30-second total floor. Extended NVIDIA validation starts with 30 and 300 seconds on WSL2 or 10 and 300 seconds elsewhere, so an override must exceed each existing deadline to raise it.

Increase the Local Validation Timeout

For validation paths that read NEMOCLAW_LOCAL_INFERENCE_TIMEOUT, raise it when the inference-server validation request needs more than 180 seconds. Large prompts, cold local model loads, and slower hardware can require a larger budget.

export NEMOCLAW_LOCAL_INFERENCE_TIMEOUT=300
nemo-deepagents onboard

Local Ollama setup treats host-side curl timeouts as retryable probe failures and retries with a larger timeout before reporting validation failure. This variable does not extend the later sandbox-readiness wait.

Increase the Sandbox Readiness Timeout

Raise NEMOCLAW_SANDBOX_READY_TIMEOUT when onboarding creates the sandbox but image build, upload, or boot exceeds 180 seconds. This can occur during a first run with cold caches or on a remote VM over a slow link.

export NEMOCLAW_SANDBOX_READY_TIMEOUT=600
nemo-deepagents onboard

Increase the Recovery Wait

Set NEMOCLAW_GATEWAY_RECOVERY_WAIT_SECONDS when OpenShell needs more than 120 seconds to re-register the sandbox after onboarding applies policy presets.

Raise both onboarding budgets when the provider probe and the later sandbox creation phase are slow.

export NEMOCLAW_LOCAL_INFERENCE_TIMEOUT=300
export NEMOCLAW_SANDBOX_READY_TIMEOUT=600
nemo-deepagents onboard