Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#3,240 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
rust, typescript
Domaine
api, backend-api-design

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
2.3k
Forks
236
Merge moyen
2 h 39 min
PR mergées (30 j)
515

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de GCWing/OpenBitFun

Toutes les issues de GCWing/OpenBitFun

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.