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

Open
#2,562 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

question

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.

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 12h
Merged PRs (30d)
133

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.