Skip to content

docs(model-rules): models.dev 作为模型信息的维护来源 - #189

Merged
Slacker-LLC merged 1 commit into
mainfrom
docs/models-dev-source
Oct 10, 2026
Merged

Slacker-LLC merged 1 commit into
mainfrom
docs/models-dev-source

Conversation

@Slacker-LLC

Copy link
Copy Markdown
Owner

内容

docs/development/MODEL-RULES.md 新增一节,把 models.dev 写成维护模型信息的首选来源(只改文档,没有代码改动)。

  • 现状事实:App 已经在用 models.dev(打包快照 + 48 小时磁盘缓存 + 离线回退),每次刷新服务商模型列表都会用它补全上下文窗口、输出上限、思考档位、模态等。
  • 一张表写清每个属性从哪来、按什么顺序取(models.dev → 规则 → 启发式)。
  • 新增模型的工作流:跑 scripts/update_models_dev.sh → 在 models.dev 查 id → 只为目录缺的或错的内容加规则。
  • 限制:社区维护不是权威(同一个 id 在不同服务商下能力不一致);它说"模型能做什么",不说"账号能调用什么"(Codex / Antigravity 以后端自己的列表为准);价格是标价,订阅与免费额度需标注为估算。
  • 快照里还有 App 暂未读取的字段:cost、tool_call、temperature、structured_output、knowledge、status、open_weights。文档明确写了"尚未实现",不承诺功能。

验证

  • 文档里的解析顺序对照 ModelsDevApi.kt、LLMModel.contextWindowTokens、ModelReleaseIndex、ThinkingLevelCatalog 源码核对过。
  • 字段清单对照 assets/models-dev-api.json 实测(193 家服务商、7248 个模型)。
  • 未跑测试:纯文档。

🤖 Generated with Claude Code

https://claude.ai/code/session_01PV4ECd3Yzu9k81sw7vHjS3


Generated by Claude Code

…ing model metadata

Record which properties come from models.dev and which stay in model-rules.json,
the resolution order for each, the limits of the catalog, and the fields the
snapshot carries that the app does not read yet.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01PV4ECd3Yzu9k81sw7vHjS3
@Slacker-LLC
Slacker-LLC merged commit 31f6940 into main Oct 10, 2026
12 checks passed
@Slacker-LLC
Slacker-LLC deleted the docs/models-dev-source branch October 10, 2026 17:05
Slacker-LLC pushed a commit that referenced this pull request Oct 10, 2026
#186, #188 and #189 landed on main. The merge was clean (CHANGELOG, 06-CURRENT-GAPS
and the string files only had adjacent additions); CI on this head tests the combination.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01PV4ECd3Yzu9k81sw7vHjS3
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.

2 participants