Troubleshooting

401: key not valid

1. Check that you used the Gameron customer key, with no extra spaces or quotes in its value.
2. Confirm the provider points to api.gameron.me and reads the environment variable you actually set.
3. Close old terminals and start a new session after changing a saved key. In PowerShell, set $env:GAMERON_API_KEY for the current terminal.
4. Check the key on the balance page. Contact support with the GM reference if it still fails.

403 / 404: expiry, allowance, or model access

Read the specific error code. An expired key needs renewal; exhausted allowance needs a top-up. For a model error, use an exact ID returned by /v1/models. Check spelling, version, and whether the selected model belongs to your plan.

Write or Bash blocked in Claude Code

Open /permissions and check the active mode. Auto mode can block a write or command when its permission-classifier model is unavailable, even when the main model answers correctly. Check that the configured Sonnet ID is authorized and update any stale project or user settings.

1. Use the supported claude-sonnet-5-5 ID for the Sonnet default when included in your key.
2. Restart Claude Code and retry a harmless file-list task in a test folder.
3. For an unavailable auto classifier, use default approval mode and approve the requested action manually.
4. Check project deny rules, managed settings, and local shell installation. Share the exact tool error if it continues.

429 / 503 or an interrupted stream

Wait briefly after a capacity rejection and respect Retry-After when present. For an interrupted generation, first inspect any saved output or completed tool action before repeating the request. Send persistent failures to support with the GM request reference.

Check the client installation

Use the update method for your installation. Multiple installations can leave an older binary first on your PATH. Include your operating system and client version when reporting an issue.

claude --version
codex --version