Gateway doctor
Diagnose Agent Gateway problems. Use when the user reports that `agw claude` fails, the proxy will not start, a model is unavailable or unauthorized, a provider looks logged out, a port is in use, or they ask to "check/diagnose the gateway", "why is agw broken", or "gateway doctor". Runs `agw doctor` and interprets the results.From its SKILL.md
npx -y skills add JuLius5838/agw --skill gateway-doctorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Agent Gateway — doctor
Diagnose and explain gateway issues without ever revealing secrets.
What to do
-
Run diagnostics:
agw doctorIt reports prerequisite versions, runtime paths and permissions, native Claude resolution, configured models, provider authentication state, an inspectable Claude
availableModelsconflict (if any), and managed-proxy state. It exits non-zero if it finds a blocking problem. Secrets are always redacted. -
Map each failing check to an action:
- provider not authenticated / expired →
agw auth chatgpt. - native claude not found → install Claude Code, then
agw setup. - port in use by an unrelated process → free the port or change
portin~/.config/agent-gateway/config.yaml, thenagw proxy restart. - proxy running with a different config/version →
agw proxy restart(the only path that applies a changed fingerprint). - availableModels excludes a configured model → this is managed Claude policy the gateway cannot override; per-task routing to that model is unavailable until the policy allows it. Do not claim success via a fallback model.
- bad file permissions → re-run
agw setup, which restores 0700/0600.
- provider not authenticated / expired →
-
Inspect sanitized logs if needed:
agw status # proxy identity + model→provider mapping agw logs --lines 100agw logsshows only sanitized operational lines (lifecycle, public model, provider, latency, error category) — never prompts, tool bodies, or secrets.
Notes
- Never suggest editing managed Claude policy to force a model.
- If a model fails
agw models verify, report it as unusable for Claude Code for that exact public name — the gateway never silently falls back to another model.