Switch Inference Providers
Move a sandbox to another provider family while keeping the OpenShell route, agent configuration, and host registry aligned. Use onboarding first when the target provider is not registered.
Find a Registered Provider
Switch the Provider at Runtime
Recreate a Deep Agents Sandbox
Deep Agents uses fresh sandbox recreation for provider changes.
The recreation validates the provider and rewrites /sandbox/.deepagents/config.toml with the OpenShell route.
Handle Compatible Endpoints
Account for Shared Gateways
Every sandbox registered on one OpenShell gateway must use the same provider and model. Custom routes must also use the same normalized endpoint and API family. NemoClaw includes stopped sandboxes because they depend on that route when restarted.
When a route conflicts, NemoClaw exits before changing the gateway, agent configuration, or host registry and names the affected sandboxes.
Align the routes, remove a conflicting sandbox, or onboard it with another NEMOCLAW_GATEWAY_PORT.
Do not run openshell inference set directly on a shared NemoClaw gateway because that bypasses registry compatibility checks.
Related Topics
- View the Active Inference Route to inspect the route before and after a switch.
- Switch Models when the provider does not change.
- Set Up an OpenAI-Compatible Endpoint to register a custom route through onboarding.