glm-5.3 is listed as an OpenHands-provider model, but the OpenHands LLM proxy rejects it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 46/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- backend-api-design
Research direction
Start by querying the OpenHands proxy’s /v1/models with a regular OpenHands LLM key and record which GLM models it serves. Then read openhands-sdk/openhands/sdk/llm/utils/verified_models.py and tests/sdk/llm/test_model_list.py; remove only unserved GLM entries from VERIFIED_OPENHANDS_MODELS, keeping the other provider lists unchanged. Done means the model-list tests pass and /llm/models/verified no longer offers removed models under OpenHands.
Written by the indexing model from the issue text.
Description
What happened
On Agent Canvas 1.41.0 (local): Settings → LLM → Add LLM Profile → provider OpenHands → model glm-5.3 → Save. It fails with:
litellm.BadRequestError: Litellm_proxyException - /chat/completions: Invalid model name passed in model=glm-5.3. Call `/v1/models` to view available models for your key.
Why it happens
glm-5.3 is in VERIFIED_OPENHANDS_MODELS, the list of models the openhands/ provider serves, so Canvas offers it in the model picker. But the OpenHands LLM proxy doesn't serve it for a regular OpenHands LLM key.
Expected
Either serve glm-5.3 on the proxy, or remove it from VERIFIED_OPENHANDS_MODELS so it isn't offered.
OpenHands AI triage
The following comments and acceptance criteria were added by the OpenHands AI agent.
Triage
Verified on main: glm-5.3, glm-5.3-flash, glm-5.3-flashx and glm-5.2 are in VERIFIED_OPENHANDS_MODELS (openhands-sdk/openhands/sdk/llm/utils/verified_models.py), which feeds both the model picker (agent-server GET /llm/models/verified) and the openhands/ provider allowlist (openhands_provider.py). The OpenHands LLM proxy is a separate deployed service; this repository cannot add models to it, so "serve glm-5.3 on the proxy" is a non-goal here. The repository-owned fix is to keep the openhands/ list aligned with what the proxy actually serves, which is the resolution used for the identical claude-opus-4-5 failure (PR #3421): remove the proxy-unserved entries from VERIFIED_OPENHANDS_MODELS only.
The GLM entries entered this list via the rolling model-list automation, whose evidence was LiteLLM model_cost plus OpenRouter availability — neither confirms OpenHands-proxy serving; kimi-for-coding is already excluded from the OpenHands list for exactly this reason. The four GLM entries stay in VERIFIED_GLM_MODELS, VERIFIED_OPENROUTER_MODELS and VERIFIED_DIGITALOCEAN_MODELS, and model_features.py is untouched, so direct GLM/BYOK, OpenRouter and DigitalOcean users are unaffected. The served-set question is settled empirically, not by policy: whoever implements must first query the proxy's /v1/models with a regular OpenHands LLM key.
Non-goals: changing the deployed OpenHands LLM proxy or its catalog; changing VERIFIED_GLM_MODELS, VERIFIED_OPENROUTER_MODELS, VERIFIED_DIGITALOCEAN_MODELS or model_features.py; changing how the openhands/ provider allowlist or /llm/models/verified works; adding curation automation; touching the clients/typescript surfaces (no contract change — the list is data).
If the proxy turns out to serve glm-5.3 (i.e., the report's environment was a transient proxy issue), stop and re-triage instead of applying the removal — the served-set observation in the implementation evidence decides which entries go.
Acceptance Criteria
- Before any list change, the proxy catalog is queried with a regular OpenHands LLM key (
GET https://llm-proxy.app.all-hands.dev/v1/models), and the query result (which, if any, ofglm-5.3,glm-5.3-flash,glm-5.3-flashx,glm-5.2appear) is recorded in the PR. - Every GLM entry in
VERIFIED_OPENHANDS_MODELSthat the queried proxy catalog does not serve is removed, and every entry that it does serve is kept. If the proxy servesglm-5.3, the issue is instead closed as not reproducible with a comment recording the catalog evidence. -
VERIFIED_GLM_MODELS,VERIFIED_OPENROUTER_MODELSandVERIFIED_DIGITALOCEAN_MODELSstill contain the GLM entries (unchanged), so direct-provider and OpenRouter/DigitalOcean pickers keep offering them. -
uv run pytest tests/sdk/llm/test_model_list.pypasses, includingtest_openhands_models_all_have_provider_listandtest_verified_lists_keep_two_latest_versions_per_line. - A saved profile using
openhands/glm-5.3from a pre-fix build still loads after upgrading (no migration error); ifopenhands/glm-5.3was removed from the list, such a profile's next LLM call surfaces the proxy's invalid-model error as before (the list is data only; no runtime allowlist behavior change is added or removed). -
GET /llm/models/verifiedon an agent-server running the fixed build no longer offers the removed GLM models under theopenhandsprovider, demonstrated with the route response.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 797
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 354
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenHands/software-agent-sdk
-
[Bug]: `list_directory` reports a complete listing as truncated when a directory has exactly 500 entriesPossibly taken @balabommablock-cpu claimed this 29 days ago. Openbug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
OpenHands/software-agent-sdk#6133 ·
Maintainers usually reply within 1 day
-
[Bug]: Command hook that exits 1 is treated as blocking when its stdout is a JSON `deny` or `continue: false`Possibly taken A pull request linked to this issue is open or already merged. Openbug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/software-agent-sdk#6116 · 3 comments ·
Maintainers usually reply within 1 day
-
[Bug]: TypeScript GET-with-body requests remain pending after a truncated responsePossibly taken @BlueRaddish claimed this 34 days ago. Openbug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OpenHands/software-agent-sdk#6059 ·
Maintainers usually reply within 1 day
-
[Bug]: Document whether `prompt_tokens` includes `cache_read_tokens` in accumulated token usagePossibly taken @Jaxon1216 claimed this 36 days ago. Openpriority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/software-agent-sdk#5975 ·
Maintainers usually reply within 1 day
-
priority:low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/software-agent-sdk#5708 · 1 comment ·
Maintainers usually reply within 1 day
All issues in OpenHands/software-agent-sdk
Similar issues
-
[Bug]: reme CLI crashes when the running server used a relative config pathPossibly taken @nurlanmnn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/ReMe#770 ·
Maintainers usually reply within 1 day
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
sickn33/agentic-awesome-skills#2437 ·
Maintainers usually reply within 1 day
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ethereum/consensus-specs#5846 ·
Maintainers usually reply within 1 day