You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a short LLMTR section to docs/local-openai-compatible-providers.md, next to the OmniRoute one (#3283). Disclosure: I maintain LLMTR.
LLMTR is an OpenAI-compatible gateway at https://llmtr.com/v1 with Bearer keys (llmtr-...). Claw already works with it through OPENAI_BASE_URL and OPENAI_API_KEY; the docs just need to cover three things that trip people up:
Some ids already start with the gateway name (llmtr/qwen3-8-27b). With local/llmtr/qwen3-8-27b, the local/ hatch is removed and the llmtr/ prefix is sent as-is.
A bare qwen/... id is a DashScope route, so vendor-prefixed ids need local/ too.
Claw asks for up to 64,000 output tokens on this route. LLMTR returns a 400 when max_tokens is above a model's output limit, so e.g. local/qwen/qwen3.8-27b-free (cap 16,384) fails today:
error: api returned 400 Bad Request (invalid_request): "qwen/qwen3.8-27b-free" can return at most 16,384 tokens in one response, but "max_tokens" was 64,000.
Thanks for the proposal and the detailed notes — the merged docs (#3373) cover the key pitfalls well: the local/ hatch removal for gateway-prefixed ids and the 64k max_tokens cap causing 400s on lower-cap models like qwen3.8-27b-free. The working example with local/llmtr/qwen3-8-27b makes it reproducible. Closing as completed.
Activity
XinwangTao commentedon Nov 5, 2026
Thanks for the proposal and the detailed notes — the merged docs (#3373) cover the key pitfalls well: the
local/hatch removal for gateway-prefixed ids and the 64k max_tokens cap causing 400s on lower-cap models like qwen3.8-27b-free. The working example withlocal/llmtr/qwen3-8-27bmakes it reproducible. Closing as completed.