Skip to content

fix(provider): route Auto through native live catalogue pooling - #22

Merged
TheStreamCode merged 2 commits into
mainfrom
fix/auto-native-routing
Aug 23, 2026
Merged

fix(provider): route Auto through native live catalogue pooling#22
TheStreamCode merged 2 commits into
mainfrom
fix/auto-native-routing

Conversation

@TheStreamCode

Copy link
Copy Markdown
Owner

Summary

Auto was sending model-router to the retired Vercel deployment (DEPLOYMENT_NOT_FOUND). It now sends Chutes' native default alias to llm.chutes.ai and, if the account has no saved routing pool, retries once with a live inline pool built from the current catalogue (:latency).

Test plan

  • npm run check (47/47 tests)
  • New tests fail without the provider change
  • Install chutes-model-provider-vscode-0.4.6.vsix and send a message with Auto (router)

The standalone router deployment is gone: model-router-ten.vercel.app
answers DEPLOYMENT_NOT_FOUND, so every Auto request failed with an
HTTP 404. Chutes resolves routing natively on the inference host now -
the saved-pool alias \default\ - so Auto sends that alias to the same
OpenAI-compatible host as concrete models, and steps down once to a
compiled-in inline pool (Qwen/Qwen3.5-397B-A17B-TEE,
zai-org/GLM-5.2-TEE) when the account has no routing pool saved at
chutes.ai/app. The virtual picker id and every setting id stay as they
were; only the routerEndpoint default moves (llm.chutes.ai/v1), since
the old value pointed at a dead deployment.
A compiled-in pair of model ids goes stale the next time Chutes retires
one. After the dashboard alias fails to resolve, list the current
catalogue and retry with those chat-capable ids plus :latency so Chutes
picks the fastest warm member and failovers to the next.
@TheStreamCode
TheStreamCode merged commit 2497dbe into main Aug 23, 2026
5 checks passed
@TheStreamCode
TheStreamCode deleted the fix/auto-native-routing branch August 23, 2026 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant