Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Feature]: Model-limit metadata for a Tsubasa provider entry

オープン
  • 何か問題がありますか？
#3,240 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
rust, typescript
領域
api, backend-api-design

調査の方向性

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:

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分
マージ済み PR（30日）
498

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

GCWing/OpenBitFun のほかの issue

GCWing/OpenBitFun の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。