Repository navigation
metrics: add session_summary to MetricsRecordingHeader - #1884
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 2d40f46 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This was referenced Oct 22, 2026
jmcclanahan
marked this pull request as ready for review
October 22, 2026 20:01
JustinScitech
approved these changes
Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
string session_summary = 11toMetricsRecordingHeader: a JSON object of session facts, at most 16 KiB.github.com/livekit/protocoland@livekit/protocol.Why
Agent evals choose which sessions to score from facts the SDK knows at upload time (agent name, tags, duration, user turns, usage). One JSON field means a new fact needs only an SDK change and an agent-evals change, not another protocol release.
How
recording_index.metadatawithout reading individual keys.evalschema/session-summary.schema.json).Depends on
Nothing. The cloud-observability and SDK PRs depend on this one.
🤖 Generated with Claude Code