github / github/copilot-sdk

SDK model listing

オープン
#2,237 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
enhancement
主要言語
Java
スター
10.5k
フォーク
1.5k
平均マージ
1日 11時間
マージ済み PR(30日)
127

説明

## Summary

Add SDK support for listing available models so applications embedding the SDK can discover which models they can use without spinning up the full agent harness. Fabric is the first concrete consumer waiting on this.

## Motivation

Some clients want to embed the SDK and use lightweight primitives (model discovery, inference) without loading the whole harness. Today the only path to model information requires standing up a full session, which is heavier than these clients need.

There are two distinct cohorts:

- **Harness customers that also want primitives.** They run the harness *and* want lightweight primitives like model listing. This issue covers this cohort.

- **Non-harness customers** A separate problem that needs its own discovery — how large the base is and what they require. *(tracked separately.)*

The direction is that the SDK is the front door: clients converge on the SDK rather than integrating against the underlying inference API directly.

## Proposed behavior

- A lightweight "list models" call available across the SDK languages that does **not** require creating a full session.

- A bounded, documented model-list schema (we don't expose the full underlying model set).

- Telemetry/headers that identify the hosting client, following the code-completions pattern for distinguishing embedding applications.

- A scaling story for identity/auth that doesn't require minting a per-client integration ID.

## Open questions

- Where does model listing live — the language-specific SDK or the core runtime?

- What exactly do we expose for model access?

## Next steps

- Nail down Fabric's actual requirements (must-have vs. nice-to-have).

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

The issue names no files, tests, or entry points. Start by clarifying Fabric's must-have requirements and resolving where model listing belongs, what the bounded schema exposes, and how hosting-client telemetry and identity should work; done means an agreed implementation direction for a lightweight SDK call across the SDK languages.

索引モデルが issue の本文から書いたものです。

評価

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

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

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