[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 小時 新手友好度 88/100
aws-samples/sample-pacer#76 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
axodotdev/cargo-dist#2523 ·
維護者通常 2 天內回覆