debug-inference

To debug OpenShell inference failures, run a structured diagnostic workflow to check gateway status, managed inference configurations, and provider records for inference.local. This process isolates root causes and provides actionable remediation steps to restore endpoint reachability.

Endpoint verification for inference.local fails due to gateway topology issues, misconfigured managed inference settings, or network policy restrictions. Diagnosing the active gateway's inference path and sandbox probing helps identify the specific protocol mismatch or unreachable host causing the failure.

Fixing a misconfigured OPENAI_BASE_URL requires verifying external provider records and host reachability through sandbox probing. The diagnostic workflow checks network policies and gateway routing to produce a corrected, hot-reloadable configuration for the external endpoint.

Yes, you can diagnose external provider routing issues by verifying gateway status and checking provider records against network policies. The debugger isolates whether the failure stems from the gateway, the external provider, or a protocol mismatch.

The best way to isolate gateway topology problems is to determine whether inference is managed internally or external, then stepwise check gateway status and sandbox probes. This structured approach identifies routing concerns and suggests concrete remediation commands.

When OpenShell inference stops working after network policy changes, check host reachability and sandbox probing results against the active gateway configuration. The debugger identifies blocked paths and generates a hot-reloadable configuration to restore connectivity.