新增provider选择从known third party provider，会报错

[panandicoding]

What version of Kimi Code is running?

0.29.2

Which open platform/subscription were you using?

Kimi Code (OAuth)

Which model were you using?

longcat2.0

What platform is your computer?

win11

What issue are you seeing?

新增provider选择从known third party provider，会报错,Fetching catalog from https://models.dev/api.json会报错
Failed to load catalog.
Error: Failed to fetch catalog: fetch failed

What steps can reproduce the bug?

everytimes

What is the expected behavior?

修复bug

Additional information

No response

[likemoongg]

I’m getting the same error. It seems like https://models.dev/ isn’t accessible in China without a VPN. Perhaps Kimi-Code could include a default list as a fallback option.

[God-archer]

我也遇到同样的错误。看起来 https://models.dev/ 在中国没有VPN是无法访问的。也许Kimi-Code可以包含默认列表作为备选方案。

即使开了梯子也无法访问，但是可以手动curl到..

[mangeshraut712]

Working on a fix: the release build already embeds a pruned models.dev snapshot (__KIMI_CODE_BUILT_IN_CATALOG__), and kap-server already falls back to it — but the TUI /provider “Known third-party provider” path and kimi provider catalog CLI only called fetchCatalog with no fallback, so networks that cannot reach models.dev failed hard.

Plan: on default-URL fetch failure, use loadBuiltInCatalog and continue with a clear “built-in snapshot” status; custom --url overrides still fail loudly; user abort does not fall back.

[likemoongg]

Kimi uses a system proxy by setting HTTPS_PROXY=http://xxxxxx in bash , according to the documentation.