[Feature]: Model-limit metadata for a Tsubasa provider entry
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- rust, typescript
调研方向
Start with src/crates/assembly/core/src/infrastructure/ai/provider_catalog.rs and src/shared/ai-provider-catalog/providers.json to understand overlay limits and fallback behavior. Then inspect OpenBitFun-Installer/src/data/modelProviders.ts and src/crates/adapters/ai-adapters/src/providers/openai/chat.rs. Done means the supported representation for Tsubasa's limits and capabilities is decided, with compatibility and request/response acceptance checks identified.
由索引模型根据 Issue 内容生成。
描述
Problem / opportunity
Tsubasa exposes two public Chat Completions model aliases, tsubasa-fast and tsubasa-pro. A named entry could reduce manual endpoint/model setup across OpenBitFun's provider catalog and Installer, but a bare provider overlay would not carry their 32,768-token context limits.
Proposed behavior
Please advise on the supported place for service-owned model limits before a provider contribution is implemented.
The proposed endpoint is https://api.tsubasa.sh/v1, using the existing openai Chat Completions adapter and a user-supplied Tsubasa API key. Fast has a maximum output of 8,192 tokens and Pro 16,384; both have a 32,768-token context window. The initial profile should expose text chat without asserting tool, vision, or reasoning support. The public aliases should remain unchanged, with no fabricated release dates or private underlying model identities.
The current overlay can list model IDs, but ModelPolicyOverlay has no limit fields and curated_model_fallback returns limits: None. Tsubasa has no models.dev provider row to supply those facts. A record that only fills curated_models therefore does not establish correct budget metadata. Is a small, backward-compatible overlay metadata extension appropriate, or should this remain a documented manual provider until the catalog can represent those limits?
Product surface
AI provider / model adapter
Details, examples, or constraints
Inspected at a0d4437e96cc663476ac1557ea9856cae626c2e4:
- Shared provider overlay.
- Overlay schema and fallback projection.
- Installer template consumer.
- Existing Chat Completions request builder.
Acceptance checks would cover catalog limits/capabilities, existing configuration compatibility, Installer/Web UI selection, exact Chat Completions request serialization and streamed response decoding, and rejected/missing credentials. An actual request should pass a 32K total-context check before broader agent/remote claims. Locale updates would follow the owning surfaces rather than sharing Web UI catalogs with the Installer.
This AI-assisted proposal follows the early design discussion requested by CONTRIBUTING.md. It contains no implementation or runtime test claim. Hosted inference and agent tool behavior have not been qualified; the current public model-discovery check returned HTTP 404.
- 主要语言
- Rust
- 星标
- 2.3k
- 派生
- 236
- 平均合并
- 2 小时 41 分钟
- 30 天内合并 PR
- 498
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
GCWing/OpenBitFun 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
GCWing/OpenBitFun#3213 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
GCWing/OpenBitFun#2363 ·
维护者通常 1 天内回复
-
question
难度 1/5 1 小时以内 新手友好度 78/100
GCWing/OpenBitFun#2340 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 38/100
GCWing/OpenBitFun#3246 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
GCWing/OpenBitFun#3237 · 1 条评论 ·
维护者通常 1 天内回复
查看 GCWing/OpenBitFun 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
software-challenge/player_rust#22 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
foundry-rs/foundry#17175 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
state:triage-needed
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
github/copilot-sdk#2793 ·
维护者通常 1 天内回复