github / github/copilot-sdk

Clarify model.telemetry event schema and semantics with CLI 1.0.83-5 / Go SDK v1.0.13

Ouverte
#2,562 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
question
Langage dominant
Java
Étoiles
10.5k
Forks
1.5k
Merge moyen
1 j 11 h
PR mergées (30 j)
128

Description

With GitHub Copilot CLI 1.0.83-5 and the Go Copilot SDK v1.0.13, protocol 3,
one SDK worker session emitted an event named `model.telemetry`. The Go SDK
does not define a typed event with that name and exposes unknown event data
through `RawSessionEventData`.

Our application deliberately fails closed on uncharacterized events. It stopped
that worker on this event. This is our guard's rejection, not evidence that the
SDK itself rejected an otherwise valid model response. We need to characterize
the event before deciding whether to treat it as an irrelevant projection.

The event appeared in a fresh worker configured for `claude-opus-5` with high
effort. Thirty-seven prior worker calls completed in the same application run.
The affected worker had no accepted evidence reads, report or usage observation
before the guard stopped it. The payload was not retained by the guard. A
model-free HTTP 400 response and a synthetic successful Anthropic tool response
both exercised the same CLI/SDK, but neither emitted this event.

Could you clarify:

1. The event's schema and trigger conditions in CLI 1.0.83-5.
2. Whether it is purely diagnostic, or can carry an error, route change,
truncation, cancellation or another execution-significant state.
3. Whether execution-significant states carried by it are also guaranteed to
appear in the typed session, assistant, usage or tool lifecycle events.
4. A deterministic local fixture or injected provider response that emits it
without paid inference.

We are keeping our report schema, required-read checks and lifecycle validation
unchanged while investigating. No prompts, response bodies, credentials or private
repository content are needed for this question.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start with the Go SDK v1.0.13 handling for protocol 3 and RawSessionEventData, then compare it with CLI 1.0.83-5 behavior for the model.telemetry event. Done means documenting the event schema, trigger conditions, execution significance, lifecycle guarantees, and a deterministic fixture that emits it without paid inference.

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

Évaluation

Stack technique
go
Domaine
api, documentation
Type d'issue
Documentation
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

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