debug-inference

OpenShell inference fails when gateway topology, provider configurations, or network policies are mismatched. Diagnosing these routes requires checking gateway status, inspecting provider settings, and running sandbox probes to isolate the root cause.

Diagnose OpenShell inference routing by running CLI status checks, retrieving inference and provider configurations, and executing sandbox probes to verify end-to-end connectivity. This workflow isolates failures across managed and external routes.

You can verify inference endpoint connectivity by running curl commands inside a sandbox environment. This sandbox-based probing tests end-to-end network reachability and validates that inference routes are correctly configured.

The best way to repair broken external inference routes is to follow structured diagnostic workflows that identify provider mismatches, reconfigure route settings, and validate results post-fix using sandbox probes.

The diagnostic workflow covers both managed and external inference paths. It auto-diagnoses routing failures by comparing gateway info and provider configs, then validates repairs across both inference route types.

When OpenShell inference still fails after provider reconfiguration, check gateway topology status and run sandbox probes to verify network policies. Post-fix validation ensures the reconfigured inference routes are reachable.